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: [cloud] #4: new release criteria for post-f20 cloud image
#4: new release criteria for post-f20 cloud image --+ Reporter: mattdm| Owner: roshi Type: task | Status: assigned Priority: major | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords:| --+ Comment (by mattdm): I'd like to add libX11 not pulled in by some dep as a warning flag, although not necessarily a blocker. (I'd like to test for that so we can react when it happens, which it seems to be inevitable in each release cycle.) -- Ticket URL: https://fedorahosted.org/cloud/ticket/4#comment:7 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
