Re: GCE Images with Imagefactory/oz
Hey Felipe, how are you doing? How are the RPM packages coming out? Need any help? ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging Google-Daemon
I don't want to slow your progress down, but I have on my roadmap plans to create some RHEL6 and RHEL7 images for GCE. I'm pretty sure I'll be able to user your rpm for RHEL7, but just keep in mind that someone will probrubly come behind you and put your package in EPEL6. So when you get rid of the init.d files, please do that in the spec file, and not somewhere before. That way I'll just have to make changes to the spec file and not create a new tarball or something like that. Hey Troy, one of my clients actually needs CentOS7 in GCE. I will start work on the image with virt-builder; which is the easiest tool to accomplish the job. Does this suit you as well? -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: GCE Images with Imagefactory/oz
Ok, I have a working recipe. Check it out: https://github.com/renich/gce-images-fedora/blob/master/imagefactory/f20.tdl I am using: oz-install -d3 -t 1 f20.tld oz-customize -d3 f20.tld f20date Tu generate and customize. It is missing some of the security points: - root still has a password - root is not locked - root can login with a key - ssh by password is not disabled. I am waiting for the google packages to be ready so I can lock root and all. It should be easy to do those things once they're done. +Felipe, let me know if you need help with anything. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: GCE Images with Imagefactory/oz
On Sat, Jun 28, 2014 at 5:00 PM, Richard W.M. Jones rjo...@redhat.com wrote: Sorry for the delayed reply, but yes this looks good to me. (I've not used the gc* utilities so I'm not really qualified to talk about those). Rich. Good to know, thanks a lot. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: GCE Images with Imagefactory/oz
On Wed, Jun 25, 2014 at 11:12 AM, Richard W.M. Jones rjo...@redhat.com wrote: So I've only skimmed the Google Cloud Engine docs, but this would be how you could do this with virt-builder ... $ virt-builder fedora-20 --output disk.raw --size 10G \ --install bash-completion,denyhosts,irqbalance,ntp,patch,rsyslog,yum-cron-daily \ --hostname metadata.google.internal \ --write '/etc/hosts: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 169.254.169.254 metadata.google.internal metadata ' \ # use --write or --upload for the other files --delete /etc/sysconfig/networking \ --edit '/etc/ntp.conf: /^server [1-3]\.fedora.*$/d' \ --run-command 'systemctl disable firewalld.service iptables.service' \ # (I got bored, there are more commands ...) $ tar zcf fedora-20.tar.gz disk.raw No root needed! Rich. Oh, please, check out my version of things here: https://github.com/renich/gce-images-fedora/tree/master/virt-builder I'd love a review by the creator! ;) I tried to keep the command not so bloated. I used a --firstboot command to put everything I could in the script. At least things that don't require scripts as parameters. The build is the command and setup is the script to follow; very much ike a post-install section on a kickstart. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
GCE Images with Imagefactory/oz
Ok, playing around with the mighty oz-install now. https://github.com/renich/gce-images-fedora/blob/master/imagefactory/f20.tdl My only problem is the ssh-fix command; since lxml caught all the redirections; namely . It doesn't like an lt; with a space next to it. https://github.com/renich/gce-images-fedora/blob/master/imagefactory/f20.tdl#L141 I'm trying to use lt; to see if the script still works... gulp... Also, the image build (even a vanilla one) hangs there and oz-install ends up complaining that the hard drive was innactive for 400 secs. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: GCE Images with Imagefactory/oz
The ppm image, in case somebody's interested: http://23.251.155.37/fedora/ss/ Also, any tips viewing these? I just use display image but it's kind of odd that a 4 MB image shows only that. Maybe it's animated and I don't know? ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora @ Google Cloud
On Mon, Jun 23, 2014 at 9:50 AM, Andy Grimm agr...@gmail.com wrote: This is very possible and should not be much work. cloud-init already is smart enough to determine it's on GCE and use the GCE data source to grab data from the metadata service. It's been a while since I've dug into the cloud-init code, but it should be trivial write some special metadata if the GCE datasource is active, and then have a config module that starts services if those special metadata bits are present (might mean writing to dbus or something to do it the right way from systemd's perspective.) If you're gonna hop into cloud-init, please, let the Googler's @ https://github.com/GoogleCloudPlatform/compute-image-packages know that you are. They might just get interested. In my experience, the google metadata thing does not do much. Just takes care of injecting keys, setting up hostname and helping with unmounting of disks; which Fedora does without it's help. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora @ Google Cloud
Hey guys, can somebody share the location of the current f20 tdl? ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging Google-Daemon
On Tue, Jun 24, 2014 at 8:15 AM, Filipe Brandenburger filbran...@google.com wrote: Hi Renich, I think you directed the message at me alone and not the mailing list... Whoops! Sorry! Let's keep it on the mailing list. On Tue, Jun 24, 2014 at 6:03 AM, Renich Bon Ciric ren...@woralelandia.com wrote: Ok, here're the SRPM, RPM and SPEC files: http://23.251.155.37/fedora/ I'm trying it out on that same server and it works, so far. It seems to work at least. Nice! I'll check them out. Anyone interested in reviewing? One minor nitpick... I think the name google-daemon is a bit too generic and doesn't convey the idea that this is relevant for the google *cloud* :-) The CentOS image calls it google-compute-daemon: $ rpm -qa google\* google-startup-scripts-1.1.3-1.noarch google-compute-daemon-1.1.3-1.noarch Which is also what the release tarballs are called: https://github.com/GoogleCloudPlatform/compute-image-packages/releases I'll change the name then. BTW, it seems that 1.1.4 is out, I believe that one will include the systemd config, maybe you could update it to use the released 1.1.4 instead of a git commit later than the tagged based as the initial point for your package(s). Cheers! Ok, I'll update it. The reason for the latter commit is that it fixed some issue that was critical. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging Google-Daemon
Ok, check them out: http://23.251.155.37/fedora/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora @ Google Cloud
On Tue, Jun 24, 2014 at 8:33 AM, Filipe Brandenburger filbran...@google.com wrote: On Tue, Jun 24, 2014 at 6:27 AM, Renich Bon Ciric ren...@woralelandia.com wrote: The reason they enable sudo and lock root is to keep better auditing options. But, hey, it's not like you're gonna create 20 keys in a single server for 20 admins to go in and do stuff. Huh, it kind of is... If you create a project and add many users to it, all of them will get accounts created by google-compute-daemon, so in effect every user of the project will be able to login to every compute instance. I currently work on a project with 5 users and all of us can log in to all instances. If someone else comes along to the project, we just add them and they get access to all instances automatically. My only problem with that is that it will create passwordless sudo for all of them. I don't think you want 20 admins in a 20 user server. My point is that, usually, one is admin and he delegates (through sudo, perms and gorups, ACL, SELinux, etc). I can live with SSH keys injected to root. A root with it's SSH allowing login without-password only. This would be convenient and no passwords involved. I see value in keeping home directories for each user... For instance, that means I don't *have* to be root all the time and I don't run the risk of typing a mistaken command and hosing the box... It also means I can customize my home with a .bashrc, .vimrc, .gitconfig without worrying about my colleagues logging in to that box and being annoyed by my settings taking over. Oh, I agree with you! No need to be root all the time. I'd create mortal user account as well; use root only for admin stuff. But, in the current design, every account you create is root; If they use sudo. That's not so cool... Also, if you're root, you can have ~/.vimrc and ~/.gitconfig without them poluting your users' environment. ;) -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora @ Google Cloud
On Fri, Jun 20, 2014 at 3:04 AM, Garrett Holmstrom gho...@fedoraproject.org wrote: I believe cloud-init treats user-data attributes the same way it treats user-data in EC2, so if that works then that would give us a fairly painless way to install or configure whatever is holding testing back. Perhaps that would be a suitable next step to try for. Since it runs at boot time and goes away cloud-init could be made to replace the startup scripts if it isn't already sufficient. I doubt it can replace the daemons in a reasonable manner without a decent amount of work, though -- the way GCE expects instances to work with metadata is somewhat unusual, and cloud-init simply isn't built to handle that (yet). Assuming there is enough interest, though, I might be interested in working on something relatively portable that can do things like mounting disks based on metadata since that would be useful to me on EC2 as well. With any luck that sort of thing could potentially even go on the stock Fedora image, too. Well, actually, vanilla Fedora is able to mount HDDs and take them away. It's KVM/Qemu in the end (I think). So, basically, the daemons manage SSH keys, sudo entries and hostname. That's all for now... I think... I've successfully tested them on Fedora. They're already packaged (twice, by the way) and tested. There is a thread on this list where I... let myself go, hehe. The license is ASL 2.0 and I think we could have it in the repos. The init scripts, though, I haven't checked. But I see some references to firstboot and other stuff that make them seem odd. I need to learn more of them. Also, I need to learn more about cloud-init so to see what services does it render useless. Knowing this, I'd, gladly, try to convince the google guys of not doing duplicate work... not that my reputation precedes me or anything (thankfully!) but I'd like to try. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Packaging Google-Daemon
So, basically, we have these files: /etc/init.d/google-accounts-manager /etc/init.d/google-address-manager /etc/init/google-accounts-manager-service.conf /etc/init/google-accounts-manager-task.conf /etc/init/google-address-manager.conf /usr/lib/systemd/system/google-address-manager.service /usr/lib/systemd/system/google-accounts-manager.service /usr/share/google/google_daemon/accounts_manager_daemon.py /usr/share/google/google_daemon/address_manager.py /usr/share/google/google_daemon/utils.py /usr/share/google/google_daemon/manage_accounts.py /usr/share/google/google_daemon/desired_accounts.py /usr/share/google/google_daemon/accounts_manager.py /usr/share/google/google_daemon/accounts.py /usr/share/google/google_daemon/manage_addresses.py My proposal: /etc/init.d/google-accounts-manager /etc/init.d/google-address-manager No need for these. We can delete them... right? /etc/init/google-accounts-manager-service.conf /etc/init/google-accounts-manager-task.conf /etc/init/google-address-manager.conf Maybe these should go in /etc/sysconfig /usr/lib/systemd/system/google-address-manager.service /usr/lib/systemd/system/google-accounts-manager.service Modify these so they point to /usr/share/google-daemon if possible. /usr/share/google/google_daemon/accounts_manager_daemon.py /usr/share/google/google_daemon/address_manager.py /usr/share/google/google_daemon/utils.py /usr/share/google/google_daemon/manage_accounts.py /usr/share/google/google_daemon/desired_accounts.py /usr/share/google/google_daemon/accounts_manager.py /usr/share/google/google_daemon/accounts.py /usr/share/google/google_daemon/manage_addresses.py Move these to /usr/share/google-daemon I'll show a spec in a little while. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging Google-Daemon
# SPEC and build script (just to fascilitate building it with mock) https://github.com/renich/fedora-packages/tree/google-daemon So, let me know what ya think. I know rsync might be a not-so-common install solution but I didn't want to type it all. Anyway, they don't provide a Makefile and they don't use submodules on the git repo; which I've already asked for in this bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/82 There is another matter. /usr/share/google_daemon instead of /usr/share/google-daemon (with a dash)... I think I can fix it in %prep but I dunno if I should. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging Google-Daemon
Ok, just patched and tested. It turns out systemd and config files where looking for stuff at /usr/share/google/google_daemon; which I deliberately moved to /usr/share/google_daemon. Installed and the daemons are up. I'll try to add some users and see what happens. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging Google-Daemon
Hah! Adding users works. Just noticed something odd. jun 19 08:07:02 localhost.localdomain accounts-from-metadata[31449]: INFO Creating account Juan jun 19 08:07:02 localhost.localdomain useradd[31451]: new group: name=Juan, GID=1004 jun 19 08:07:02 localhost.localdomain useradd[31451]: new user: name=Juan, UID=1001, GID=1004, home=/home/Juan, shell=/bin/bash jun 19 08:07:02 localhost.localdomain useradd[31451]: add 'Juan' to group 'adm' jun 19 08:07:02 localhost.localdomain useradd[31451]: add 'Juan' to group 'video' jun 19 08:07:02 localhost.localdomain useradd[31451]: add 'Juan' to group 'dip' jun 19 08:07:02 localhost.localdomain useradd[31451]: add 'Juan' to shadow group 'adm' jun 19 08:07:02 localhost.localdomain useradd[31451]: add 'Juan' to shadow group 'video' jun 19 08:07:02 localhost.localdomain useradd[31451]: add 'Juan' to shadow group 'dip' I dunno what the dip group is but... video?... Oh well... just sayin' ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging Google-Daemon
Ok, the address manager works as well; buy you need to remove /etc/hostname for it to work. Then, SELInux is gonna complain about some things related to the hostname... maybe because the file does not exist. But $HOSTNAME is set and all. Another thing is that add ssh key functionality works, but it does not remove it. I don't get messages about it on ausearch, journalctl or any log. In short, nothing happens. This is not desirable and I dunno if it's a bug of the daemon or something is blocking it. The image survives a reboot and the daemons start and stay alive. Btw, sorry if this thread seems like my journal. Just wanna keep track of things. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora @ Google Cloud
On Tue, Jun 17, 2014 at 7:09 PM, Renich Bon Ciric ren...@woralelandia.com wrote: Will do. Hope I can do it tonight and report back. Ok, kinda put my stuff into github and will start work on imagefactory/oz: https://github.com/renich/gce-images -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora @ Google Cloud
On Wed, Jun 18, 2014 at 3:49 PM, Dennis Gilmore den...@ausil.us wrote: The issue is we are trying to build one image to run in all clouds, so cloud provider specific tools are out. extend the functionality of cloud-init if you feel its useful. Ideally its something that can work in all providers. Dennis Oh, a single image for all. That will be a hard one. Cloud-init support would be, definitely, a must. The thing is that GCE support plain vanilla images. The integration with their API/Web front end is the only matter here. The image is sure to work 100%. You could handle mounting and unmounting without trouble with it. But, when it comes to integration with their API, ssh key management and stuff, the image will not behave. So, in a sense, the Google tools integrate it with thei infrastructure. Providing a package with it should be enough for it to be fully integrated. And, if we're able to detect that the image was deployed in Google's infrastructure and install the package, we'd be really cool. If not, just have some docs here and there that tell you to install them and reboot. But, if we're to upload the images to them, we should provide them fully functional and integrated. That is my, probably not-so-humble, opinion. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora @ Google Cloud
On Sat, Jun 14, 2014 at 5:22 AM, Vaidas Jablonskis jablons...@gmail.com wrote: Hey. Have fun. Btw, I have built an image already if you like to have a look: https://github.com/vaijab/fedora-gce-image Awesome! Thanks! I posted my method on my blog. I'll add a link to your repo as an alternative. Some observations, though: - You're using md5 for passwords. Google requires SHA512 https://developers.google.com/compute/docs/images#security - You did not add their metadata internal thingy on ntp and hosts: https://developers.google.com/compute/docs/images#os https://developers.google.com/compute/docs/images#network - What about their google stuff? daemon, init-scripts, etc? Does cloud-init take care of all that? Even mounting drives and stuff? If so, cool! Anyway, just some observations. Check out mine: http://blog.woralelandia.com/2014/06/14/howto-build-and-use-fedora-20-foron-google-cloud/ I like the use of kickstarts better, though. However, recently google cloud changed how DHCP configures network and I discovered that current fedora dhcpclient has some bugs, which hopefully will be fixed in the next few days. Have a look at bugzilla report for more details: https://bugzilla.redhat.com/show_bug.cgi?id=1102830 Ah, good to know. Will subscribe to it. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora @ Google Cloud
Hey guys, I'm, currently, working on a Fedora image for Google Cloud; just for fun. I'm using virt-builder. I'd like to know what tools and files are you using to build your images. I'd like to contribute it if I manage to get something useful. They have some requirements here: https://developers.google.com/compute/docs/images#buildingimage So, If I'm to use a script for virt-builder or a kickstart, I wanna help out if possible. Thank you for any feedback and you're welcome to join the fun if you like ;) -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtualization and HotPlugging/swapping
On Thu, Jan 20, 2011 at 2:31 PM, Oliver Falk oli...@linux-kernel.at wrote: Hi Renich! If there's an agenda beforehand and I can be of use in any way... Sure. :-) Also consider the TZ... Well, they're based at Zurich and I'm in Guadalajara, México so, TZ will be... Which is yours? ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Re: Virtualization and HotPlugging/swapping
On Thu, Jan 20, 2011 at 4:36 PM, Oliver Falk oli...@linux-kernel.at wrote: Zürich is fine :-) I'm in AT - GMT+1. So, you're the one who is the show stopper :-) Man, I'm a vampire; I love late-night stuff so, no problems here. I could even consider to drive there ~800 km = ~ 500 miles, while you can't. At least not by car... :-) Hahaa.. still, it's 27 ºC here @ Guadalajara in winter ;) Feel free to stop by and I'll show you around, if you'd like ;) ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Re: KVM/Qemu on CloudSigma
On Fri, Aug 27, 2010 at 10:28 PM, Garrett Holmstrom gho...@fedoraproject.org wrote: One of this SIG's goals is to help get current Fedora images onto a variety of cloud providers. As we are just starting out, EC2 happens to be the top priority, but we definitely encourage other providers to work with us to help us help them help us all provide the best Fedora experience possible. Man, I sound like a politician... LOL. Yeah, you got my vote! Anyway, glad to read what you typed! ;) I've uploaded the netinstall cd to CloudSigma. The incoming transfer is free with them so it costs nothing to install via netinstall... and the speed is astonishing! Thank you for the attention. I hope we can work with these guys since they're very accessible. It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
