Fedora 16 Beta image status
by Dennis Gilmore
Hey all,
I have images made in koji and boooting and working fine to a point.
im stuck on one issue right now. when i go to ssh in im prompted for a non
existant password, and ssh key is not being accepted.
im using the attached kickstart file to create the image i have appended
"idle=nomwait" to the boot line to have booting working
Dennis
12 years, 7 months
Re: Yum S3 plugin
by Jorge Gallegos
Hi,
On Thu, Sep 15, 2011 at 11:57:51AM -0400, James Antill wrote:
> On Wed, 2011-09-14 at 21:48 -0700, Jorge Gallegos wrote:
> > So, I gather no one can shed some light on this? anyone? bueller?
> >
> > The bug (point #2) doesn't really stop the plugin from working, but it is annoying.
> >
> > Any help would be much appreciated
>
> You'd probably have been better off mailing this to the yum devel ML
> and not fedora-devel. Anyway...
*Facepalm* you're right. My apologies... I guess I gotta work a little less because I don't know what I'm thinking half the time :-/
>
> > > - Fix an annoying bug where the plugin creates an empty yum cachedir in
> > > the current directory. This is because the way the plugin works, it
> > > creates a copy of the original repo with a different grabber based on
> > > boto/urllib2 and then copies the rest of the attributes. However when
> > > the [3]new repo is created, basecachedir is empty. Can any of you fine
> > > people spot a way around that? it's been bugging me for a good week now.
>
> This is due to the switch you are doing on the repo. objects ... using
> itermitems() seems like it's clever, to get all the data from the
> swapped out repo. ... but that's actually inherited from the config.
> object, so all you are setting are the config. options.
Actually I did this because a bunch of attrs like name and etc. weren't set. I thought this would be easier than fishing for the missing attrs
> The RHN plugin just manually sets .base_persistdir, IIRC, and that will
> probably fix it for you too. For your usecase I'd be very tempted to not
> do the swapout at all (as it requires a lot of testing/etc.) as all you
> really need is to override the grab object and set a couple of things.
>
I'll take a look at the RHN plugin (should've seen that one sooner too ~.~ ) and maybe you're right... I _should_ be able to just override the grabber. I'll explore both.
Thanks a lot!
> --
> devel mailing list
> devel(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
12 years, 7 months
Cloud SIG meeting TODAY! 2011-09-16
by Robyn Bergeron
Meeting Details: Friday, 2011/09/16 @1900 UTC (In NA - East coast, 3pm; West coast, 12pm.)
Meeting channel: #fedora-meeting, irc.freenode.net
Covering your usual favorite fun (EC2, BoxGrinder, Aeolus, OpenStack, HekaFS, other features), plus touching base on the Fedora Cloud Guide / docs, and test day fun. There will be plenty of ground to cover today, feel free to stop by :)
-Robyn
12 years, 7 months
Fedora Cloud Guide sprint IRC log
by Robyn Bergeron
Hey folks,
Sparks and I and many others (thank you!) just chatted for an hour or so
in #fedora-cloud on IRC about plans for the Cloud Guide.
Notes below - you may want to read the logs as well. If you have any
ideas on anything we've missed, please feel free to add your thoughts to
this thread.
Thanks,
Robyn
Minutes:
http://meetbot.fedoraproject.org/fedora-cloud/2011-09-15/cloudy_docs_spri...
Full Log:
http://meetbot.fedoraproject.org/fedora-cloud/2011-09-15/cloudy_docs_spri...
=================================
#fedora-cloud: Cloudy Docs Sprint
=================================
Meeting started by rbergeron at 17:11:21 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-cloud/2011-09-15/cloudy_docs_spri...
.
Meeting summary
---------------
* BoxGrinder (rbergeron, 17:13:45)
* IDEA: Boxgrinder basics - what it is, how it works, etc.
(rbergeron, 17:15:03)
* IDEA: Using BoxGrinder to create a Fedora image (rbergeron,
17:15:19)
* IDEA: Using the BoxGrinder/Fedora AMI on EC2 to create a Fedora
instance on Amazon (rbergeron, 17:15:42)
* LINK: http://boxgrinder.org/ (rbergeron, 17:16:16)
* LINK:
http://boxgrinder.org/tutorials/boxgrinder-build-usage-instructions/
(rbergeron, 17:16:37)
* LINK: http://boxgrinder.org/tutorials/ (rbergeron, 17:16:55)
* IDEA: go into some of the details about OS options, platform
plugins, delivery plugsins (rbergeron, 17:17:54)
* Some of this info may be well-written out already in BG
documentation (rbergeron, 17:18:08)
* OS plugins - rhel, fedora, centos (various version) (rbergeron,
17:18:48)
* Platform plugins - virtualbox, vmware, ec2 (rbergeron, 17:19:04)
* Delivery platforms (where it can get delivered AUTOMAGICALLY) - EBS,
cloudfront for S3, sftp, ami for s3, local filesystem, s3 for s3
(rbergeron, 17:20:15)
* IDEA: Connive spevack into writing up some documentation or
something about What All These Different Amazon Things Are
(rbergeron, 17:20:33)
* LINK:
https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/...
(Sparks, 17:23:12)
* BG guys hang in #boxgrinder (rbergeron, 17:23:54)
* HekaFS (rbergeron, 17:31:54)
* LINK: https://fedoraproject.org/wiki/HekaFS (Sparks, 17:33:16)
* LINK: https://fedoraproject.org/wiki/SimpleHekaFS ksa (kkeithley,
17:33:52)
* hekafs is a layer on top of glusterfs (rbergeron, 17:40:59)
* OpenStack (rbergeron, 17:45:12)
* LINK: https://fedoraproject.org/wiki/Features/OpenStack
(rbergeron, 17:47:34)
* LINK:
https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova
(rbergeron, 17:47:53)
* OpenSTack has a few individual pieces that we have right now that
can be documented individually if we want - Nova, Swift, and Glance
(rbergeron, 17:48:36)
* Nova is management/UI/deploying of things, Swift is object storage,
and Glance is image creation (rbergeron, 17:49:20)
* LINK: http://docs.openstack.org/ (rbergeron, 17:50:06)
* LINK:
https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova
(gholms, 17:53:11)
* LINK:
https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova
(Sparks, 17:53:42)
* openstack getting started guide needs to tell you wheree to get the
euca-* commands from (rbergeron, 17:53:44)
* IDEA: Having at least some basic info about what is euca2ools might
be useful, at least WRT sections on AWS and Nova (rbergeron,
17:56:55)
* gholms can answer euca-related questions if needed. (rbergeron,
17:57:38)
* Aeolus (rbergeron, 17:57:44)
* LINK: http://aeolusproject.org/use_it.html (rbergeron, 17:58:11)
* Aeolus is made up of a bunch of different pieces - Audrey,
Conductor, Configure, ImageFactory, Image Warehouse, Oz, Spherical.
(rbergeron, 17:58:46)
* Pieces of Aeolus used in Fedora are Conductor, Configure,
ImageFactory, Image Warehouse, Oz. (rbergeron, 18:03:08)
* LINK: OZ Documentation - http://aeolusproject.org/oz.html
(rbergeron, 18:05:16)
* jclift (justin clift, aeolus comm. mgr) is probably the right person
to ask. (rbergeron, 18:05:49)
* Sheepdog (rbergeron, 18:07:26)
* LINK: http://www.osrg.net/sheepdog/ (rbergeron, 18:07:48)
* LINK: https://fedoraproject.org/wiki/Features/Sheepdog (rbergeron,
18:08:07)
* LINK: https://github.com/collie/sheepdog/wiki (rbergeron,
18:08:33)
* LINK: https://github.com/collie/sheepdog/wiki/Getting-Started
(rbergeron, 18:09:11)
* Anything else? (rbergeron, 18:10:40)
* LINK:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/C...
(rbergeron, 18:13:45)
* LINK: http://matahariproject.org/manual/ (russellb, 18:14:44)
* LINK: http://matahariproject.org/manual/ (Sparks, 18:14:53)
* Matahari would be good for "tools you can use to manage fedora
systems deployed in a cloud" (rbergeron, 18:15:00)
* Still outstanding - need info from Ian Main (slower on irc) re:
condor cloud (rbergeron, 18:18:34)
* How to get Fedora for use on EC2 (rbergeron, 18:19:13)
* We have AMIs for Fedora (knock on wood) published to EC2.
(rbergeron, 18:20:45)
* IDEA: How do we find them, where do we get the information?
(rbergeron, 18:20:55)
* IDEA: How do I get a vm started, what can i use it for, what are all
these various AWS services (rbergeron, 18:21:32)
* IDEA: Troll Max Spevack at all possible opportunities (rbergeron,
18:21:55)
Meeting ended at 18:40:15 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* rbergeron (181)
* Sparks (58)
* gholms (47)
* clalance (29)
* russellb (12)
* zoglesby (9)
* kkeithley (8)
* ke4qqq (6)
* zodbot (5)
* jsmith (4)
* msavy (3)
* mdomsch (1)
* sparks (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
12 years, 7 months
Last week's really late Cloud SIG meeting minutes
by Robyn Bergeron
Sorry about the belatedness on notes - was in Ohio for Ohio Linux Fest,
watching Build a Cloud Day (while running the meeting), so that I can
actually know what I'm talking about on occasion. :D
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2011-09-09/cloud_sig.2011...
Full Logs here:
http://meetbot.fedoraproject.org/fedora-meeting/2011-09-09/cloud_sig.2011...
==========================
#fedora-meeting: Cloud SIG
==========================
Meeting started by rbergeron at 18:59:43 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2011-09-09/cloud_sig.2011...
.
Meeting summary
---------------
* Who's here? (rbergeron, 19:00:01)
* EC2 (rbergeron, 19:01:04)
* bz 718722 needs more info (rbergeron, 19:03:06)
* ACTION: dgilmore is going to upload/test ec2 images (rbergeron,
19:14:37)
* systemd needs fixing - defaults to graphiccal.target which doesn't
work right if you don't have x installed, causes boot to hang
(rbergeron, 19:17:04)
* We shall proceed ahead and fix things as we find them :)
(rbergeron, 19:29:55)
* Aeolus (rbergeron, 19:31:16)
* latest aeolus is in f-16, will be the one that goes into beta.
(rbergeron, 19:32:00)
* LINK: http://www.youtube.com/watch?v=mOkfK89CEyE (rbergeron,
19:33:28)
* Nice video on workload manipulation using aeolus (rbergeron,
19:33:49)
* a few pkg dep problems for conductor-devel that they're working
through, but won't kill beta if they aren't available (rbergeron,
19:34:08)
* f-16 aeolus will still be using condor, condor replacement still has
2 outstanding issues (rbergeron, 19:36:57)
* HekaFS (rbergeron, 19:38:09)
* patches going upstream, not much to report in hekaFSland.
(rbergeron, 19:39:29)
* LINK: https://fedoraproject.org/wiki/SimpleHekaFS (kkeithley,
19:40:51)
* kkeithley working on a document for usage of HekaFS (rbergeron,
19:41:09)
* Has been pushed to the wiki (rbergeron, 19:41:25)
* gluster 3.2.3 is in the f16 repo (rbergeron, 19:41:59)
* latest hekafs rpm (0.7-11) should be out in another day (rbergeron,
19:42:25)
* OpenStack (rbergeron, 19:42:46)
* See openstack status mail to cloud-sig list (rbergeron, 19:46:27)
* LINK:
http://lists.fedoraproject.org/pipermail/cloud/2011-September/000813.html
(rbergeron, 19:46:37)
* tempo and nova-adminclient are nice packaging tasks available rigth
now for those interested in helping (rbergeron, 19:47:01)
* ACTION: mdomsch to apply markmc's keystone packaging patches
(rbergeron, 19:47:12)
* karma for packages in updates-testing please :) (rbergeron,
19:49:19)
* ACTION: rbergeron to get us a cloud test day reserved (rbergeron,
19:52:09)
* Any other business? (rbergeron, 19:56:43)
Meeting ended at 19:59:55 UTC.
Action Items
------------
* dgilmore is going to upload/test ec2 images
* mdomsch to apply markmc's keystone packaging patches
* rbergeron to get us a cloud test day reserved
Action Items, by person
-----------------------
* dgilmore
* dgilmore is going to upload/test ec2 images
* markmc
* mdomsch to apply markmc's keystone packaging patches
* mdomsch
* mdomsch to apply markmc's keystone packaging patches
* rbergeron
* rbergeron to get us a cloud test day reserved
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* rbergeron (108)
* dgilmore (42)
* markmc (35)
* jforbes (27)
* clalance (23)
* tflink (17)
* jgreguske (14)
* kkeithley (11)
* zodbot (9)
* mdomsch (7)
* jdarcy (2)
* jsmith (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
12 years, 7 months
Re: Yum S3 plugin
by Jorge Gallegos
So, I gather no one can shed some light on this? anyone? bueller?
The bug (point #2) doesn't really stop the plugin from working, but it is annoying.
Any help would be much appreciated
On Fri, Sep 09, 2011 at 01:03:24PM -0700, Jorge Gallegos wrote:
> (to both cloud@ and devel@)
>
> I was interested in a yum plugin to support S3, and discovered [1]this
> forum post, where Seth and James basically gave their thumbs up. The
> author (Robert Mela, even though he's not the original author either)
> made it work and there was some feedback provided, which I incorporated,
> along with a bunch of small improvements in my [2]github branch.
>
> Robert says in the forum post that he'll be happy if someone shepherds
> this into completion and I'm more than happy to try.
>
> Right now the plugin works, is a bit more aligned with the yum plugin
> architecture I think (I'd really like it to be true :) and also allows
> you to set the S3 credentials on a global, per-repo or using environment
> variables.
>
> There are 2 things I want to complete/need help with:
> - Package it as an RPM: I have a half-finished spec for this and I
> should have no problems finishing as long as I can deal with the item
> below:
> - Fix an annoying bug where the plugin creates an empty yum cachedir in
> the current directory. This is because the way the plugin works, it
> creates a copy of the original repo with a different grabber based on
> boto/urllib2 and then copies the rest of the attributes. However when
> the [3]new repo is created, basecachedir is empty. Can any of you fine
> people spot a way around that? it's been bugging me for a good week now.
>
> thoughts? comments? suggestions? let me know :)
>
> Cheers
> ~kad
>
> PS if you're asking yourselves: Why would you need this plugin if you
> can create websites off an S3 bucket? the answer is: using S3 offers
> more granularity to share, instead of just opening up the contents of
> the bucket to the entire world.
>
> [1]
> http://www.bluequartz.us/phpBB2/viewtopic.php?p=568109&sid=d3462de3a07fc6...
> [2] https://github.com/thekad/yum-s3-plugin/tree/v1.1.x
> [3] https://github.com/thekad/yum-s3-plugin/blob/v1.1.x/s3.py#L228
>
12 years, 7 months
OpenStack approved by FESCo as a feature
by Robyn Bergeron
Subject says it all.
Well, not entirely; they want us to do a test day, particularly since we
missed Alpha, which I told them was in the works. So we have to follow
through there - I'll be getting this in the queue later this afternoon
when I have a chance. :)
-Robyn
12 years, 7 months
Yum S3 plugin
by Jorge Gallegos
(to both cloud@ and devel@)
I was interested in a yum plugin to support S3, and discovered [1]this
forum post, where Seth and James basically gave their thumbs up. The
author (Robert Mela, even though he's not the original author either)
made it work and there was some feedback provided, which I incorporated,
along with a bunch of small improvements in my [2]github branch.
Robert says in the forum post that he'll be happy if someone shepherds
this into completion and I'm more than happy to try.
Right now the plugin works, is a bit more aligned with the yum plugin
architecture I think (I'd really like it to be true :) and also allows
you to set the S3 credentials on a global, per-repo or using environment
variables.
There are 2 things I want to complete/need help with:
- Package it as an RPM: I have a half-finished spec for this and I
should have no problems finishing as long as I can deal with the item
below:
- Fix an annoying bug where the plugin creates an empty yum cachedir in
the current directory. This is because the way the plugin works, it
creates a copy of the original repo with a different grabber based on
boto/urllib2 and then copies the rest of the attributes. However when
the [3]new repo is created, basecachedir is empty. Can any of you fine
people spot a way around that? it's been bugging me for a good week now.
thoughts? comments? suggestions? let me know :)
Cheers
~kad
PS if you're asking yourselves: Why would you need this plugin if you
can create websites off an S3 bucket? the answer is: using S3 offers
more granularity to share, instead of just opening up the contents of
the bucket to the entire world.
[1]
http://www.bluequartz.us/phpBB2/viewtopic.php?p=568109&sid=d3462de3a07fc6...
[2] https://github.com/thekad/yum-s3-plugin/tree/v1.1.x
[3] https://github.com/thekad/yum-s3-plugin/blob/v1.1.x/s3.py#L228
12 years, 7 months
