Packaging Google-Daemon
by Renich Bon Ciric
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/
9 years, 9 months
docker image questions!
by Matthew Miller
See https://fedorahosted.org/cloud/ticket/65
Adam asks:
What "Fedora" exactly is the image going to contain? Fedora Server?
Fedora Cloud? Will it be a part of either of those products? If not, what
is its status, exactly? Who's responsible for it? Is it considered a
primary or frontline or whatever Fedora deliverable? Who's going to test
it? How's it going to be promoted in relation to all our other
deliverables?
Here are *my* answers -- let's make sure we all agree. :)
* It will contain its own very minimal "spin". We're not (currently) going
to produce "layered" images -- just the base. (Application images will
be made via Docker's "trusted builds" service from the fedora-dockerfiles
repo, on top of this base.)
* It will initially be part of Fedora Cloud, but long term I think we want
to move it to Env & Stacks (CC'ing).
* Correspondingly, I think we're responsible.
* On "primary or frontline", I think the answer is "not release blocking",
but we'd like to produce and upload the image after release if we miss
it
* Who is going to test it? We should. Possibly, launching _this_ image
will be part of the Fedora Atomic tests?
* The goal is to upload the official image to the Docker index in a manner
similar to our other cloud images.
* We may promote it on the web site in some manner, but the primary point
is that we want to appear at <https://registry.hub.docker.com/>
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 9 months
Re: GCE Images with Imagefactory/oz
by Renich Bon Ciric
On Fri, Jun 27, 2014 at 6:18 PM, Renich Bon Ciric
<renich(a)woralelandia.com> wrote:
> A few good ideas here. I'll implement them and let you know.
I dunno why I keep replying to you and not the list, Felipe. It
catches you instead of the list. Just an OOT comment.
--
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/
9 years, 9 months
Fedora @ Google Cloud
by Renich Bon Ciric
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/
9 years, 9 months
WORKING rawhide cloud image -- let's get it in shape for alpha
by Matthew Miller
This one boots and works!
http://koji.fedoraproject.org/koji/taskinfo?taskID=7078357
On my very first test, I couldn't ssh in after boot even though the instance
was up in openstack. That's a little concerning but I can't reproduce. If
you can, that'd be awesome.
It also takes a _really_ long time to boot -- a full 65 seconds before
cloud-init is finished. Need to diagnose that. (I made a ticket. Anyone want
to grab it, awesome.)
On the good news front: the image itself is 187MB as a qcow2 and 109MB as a
raw.xz. And that's without additional extreme measures. On-disk footprint is
484M for /. (102MB of which is locale-archive. Argh!)
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 9 months
Location of Fedora cloud images
by Juerg Haefliger
All,
The current (qcow2) Fedora 20 cloud image lives at:
http://mirror.switch.ch/ftp/mirror/fedora/linux/updates/20/Images/x86_64/....
The date in the image name makes it slightly less convenient for automatic
retrieval/processing of the image. Would it be possible to rearrange the
location so that a 'latest' link always points to the latest image
directory and the image names are date-agnostic?
Something like:
20/Images/x86_64/20140407/Fedora-x86_64-20-sda.qcow2
20/Images/x86_64/20140407/Fedora-x86_64-20-sda.raw.xz
20/Images/x86_64/latest -> 20140407
Thanks
...Juerg
9 years, 10 months
gone for next meeting
by Matthew Miller
I have the next few days off for some family travel. That means I'll miss
the meeting this week. One topic that might be worth discussing is if
someone else would like to take over as FESCo liaison for Fedora Cloud. This
mostly entails coming to the FESCo meetings at least every other week and
being generaly on top of what's going on for when people ask. It also
involves some degree of being the talking head for the subproject.I think a
lot of WG members could easily do it, but it is an extra degree of
commitment
As I mentioned in my blog post
<http://fedoramagazine.org/first-thoughts-as-fedora-project-leader/>, I'm
still very interested in being involved here, but given everything else, I
think the liasion responsibility is something I could hand off to help keep
my life and schedule in some semblance of balance. Discuss at meeting? :)
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 10 months
Question on documentation location for upgrading the kernel on a Fedora AWS cloud server
by Mark C. Allman
Where is the documentation for upgrading to a newer kernel once you have
a server set up and running? You can't just run "yum upgrade" or "dnf
upgrade." I've googled around and there are all kinds of docs, blogs,
etc., on setting up a new server but I can't find anything documenting
how to update.
Just point me to the docs. I can "RTFM." ;-]
Thanks,
--
Mark C. Allman, PMP, CSM
Founder, See How You Ski, www.seehowyouski.com
Sr. Project Manager, Allman Professional Consulting, Inc.,
www.allmanpc.com
617-947-4263, Twitter: @allmanpc
9 years, 10 months
