day.
I'm around, but didn't think about this until just now (one of those
weeks!) and haven't had a chance to think about (let alone look at) what
might be an agenda. Possibly cancel this week?
--
Matthew Miller
Fedora Project Leader
nces on bare metal.
We *could* go the other way -- cloud being virt guests and server being bare
metal. From the perspective of putting together the release, that does make
some sense, but I think it's mostly a useful distinction from _that_
direction, and not so useful fro
son not to (and, if that happens, see if we can work with the upstream
project to straighten out whatever problem).
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listin
> Please let me know whether you would be interested in knowing what packages
> I put in
Yes, that'd be great!
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/
On Mon, Jul 14, 2014 at 05:09:34PM -0400, Colin Walters wrote:
> This change should be safe because the Fedora Cloud kickstart in
> spin-kickstarts uses services --enabled=cloud-init.
+1 -- and in the future, we should be using systemd presets in the cloud
image.
--
Matthew Miller
lude
> those native to the init daemon and sysv ones.
FTR, I don't think we should block on this unless it affects _all_ such
services; if it only affects an odd case, we should just migrate that
service.
Setting up a general plan for complete migration seems like a good long-term
approach.
;ve had some shifts in
people and also summer schedules are different, etc.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: htt
On Thu, Jul 10, 2014 at 05:40:33PM +0200, Haïkel wrote:
> Let's start voting !
> +1 from myself.
+1! Welcome and thanks, Andy!
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraprojec
0 to restart conversation with big data sig
* **UNASSIGNED**
* (none)
People Present (lines said)
---
* mattdm (159)
* roshi (23)
* number80 (20)
* imcleod (19)
* jzb (12)
* zodbot (9)
* agrimm (5)
* jsmith (4)
* sgallagh (3)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBo
FESCo cracks and didn't make the
change list. (I asked for it to be deferred pending the name change from
"Docker Host Image" to "Fedora Atomic", and then I didn't re-propose it.)
CC'ing Jaroslav how do you think we should best handle this? New FESCo
change tic
se are:
* http://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
* http://fedoraproject.org/wiki/Changes/Smaller_Cloud_Image_Footprint
* http://fedoraproject.org/wiki/Changes/Atomic_Cloud_Image
(Anything else?)
--
Matthew Miller
Fedora Project Leader
__
est 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
t) python anyway, it's not much of a difference.
However, I *would* like to see https://fedorahosted.org/cloud/ticket/48
resolved -- rsyslog vs. journald. See
https://bugzilla.redhat.com/show_bug.cgi?id=986511 for the gory details.
--
Matthew Mi
On-disk footprint is
484M for /. (102MB of which is locale-archive. Argh!)
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://
animated and I
> don't know?
It's just an old, very basic uncompressed format. I suggested that maybe PNG
export would be more convenient, but it's pretty low on the priority list.
:)
--
Matthew Miller
Fedora Project Leader
___
clo
tus (progress and problems, etc.) to FESCo.
The amount to which this person needs to be the "driver" of the group, or
the public face can vary. We need those things, but they really can be three
distinct roles.
--
Matthew Miller
Fedora P
F19 to F20.
I'm not sure. One thing we're planning with F21 is to redo the images with
the newer pvgrub kernel image from Amazon -- that might help. We could test
with F20 but it'd be nice to have a consistent (fails every time) case we
service with information on current and updated images (or one
can use datagrepper or the like at a more low level in the meantime).
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedorap
cket, it's mostly
useful with configuration, not in the default state.)
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code o
cloud-init requires python-cheetah. This pulls in python-pygments. This
pulls in python-pillow, which pulls in ghostscript. Then we get the whole X
stack.
Can we break this at the top?
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
s of this, and
I'd like to see a little more coordination so that we're all going in the
same direction. (And, ideally, so that we can actually have images in place
for F21 alpha.)
--
Matthew Miller
Fedora Project Leader
___
t-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
On Tue, Jun 10, 2014 at 05:51:32PM +0600, Sam Kottler wrote:
> We put cloud-init on GitHub as a mirror of Fedora's git repo to gain
> visibility and encourage contributions. How do people feel about doing
> the same for the docker-io repo?
The RPM/specfile repo? What does that gain
.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
test plan
* Automatic Smoketests on Image Build
* Deliverables and release engineering changes for Fedora.Next
* Project Atomic work tracker
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https
some things out for testing periods -- "let's try neo-cloud-init-6
this week!"
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud mailing list
c
the spin-kickstart repo,
whatever we call it. I agree that it's not really a "spin".
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud mailing
that, I think that while it'll probably _get_ those
experimental things sooner, there's enough going on with Atomic itself that
it'd be better to have a separate place to do the actual experimenting.
What do you think?
--
Matthew Miller-- Fedora Project--
; I specifically meant "metrics about whether issues are specific to one
> Fedora release or another". I should probably start drinking coffee.
Coffee is delicious. But even in a highly caffeinated state, I'm curious why
you don't think this specific thing is interesting.
degree to which I don't care about metrics :)
I think we should care about metrics, and I think this would be very useful
to track, even though I agree it'd be better to combine into one actual
process at this point.
--
Matthew Miller-- Fedora Project--
and then get the
> required test cases and matrices written between then and branching
> (which is 'no earlier than July 8' on current schedule).
As someone who is not actually volunteering to do much more than cheerlead
for this particular bit of writing, that s
is QA->WG
directly, or should it be QA says something to FESCo, FESCo works with WG?
Since parts of this are new to all of us, and other parts new to a lot of
us, maybe it'd be good to put suggested/reasonable deadlines on some parts
of the responsib
`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud mailing list
cloud@lists.fedoraproject
ess. Better,
we'll want it integrated into the planned _automatic_ process.)
Anything I'm missing here?
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
__
early.
Yep, I've got it. See eveybody in a couple of hours.
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud mailing list
cloud@lists.fedoraproject.org
On Wed, Apr 30, 2014 at 02:03:42PM -0400, Matthew Farrellee wrote:
> pile on!
> big data applications are generally scale-out, which is currently
> not easy to do w/ docker images.
Okay. I retract this one.
Maybe we'll revisit in a couple of years. :)
--
Matthew Miller--
On Wed, Apr 30, 2014 at 10:55:05AM -0500, Joe Brockmeier wrote:
> Just bumping this, as only two or three people have responded.
> (I am in, btw.)
Did I respond? I hope so. Sorry if not. I'm in. :)
--
Matthew Miller-- Fedora Project--
here at https://github.com/scollier/Fedora-Dockerfiles/pull/29)
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud mailing list
cloud@lists.fedorapr
that, and then use Docker's "trusted builds" process
to produce updated layers.
Does this make sense?
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
__
se to have a 32-bit big data image, but maybe
I'm wrong on that for certain workloads?
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud mailing list
ject.org/wiki/Cloud/Governance>
I think it's possible that we'll have a couple of new openings, and there's
always room for enthusiasm. Can you tell us a little bit more about your
interests in cloud, what you'd particularly like to help with, and etc?
It's my wife's birthday, and we're going to go off to Vermont somewhere
where there's no computers or Internet access. If there are any crises this
week, let's get them all in by Wednesday afternoon. :)
--
Matthew Miller-- Fedora Project--
I think we can use the Fedora community cloud EC2 account for this, but I
will double check. If that's not possible, I'll beg for the required budget.
We _should_ test on both OpenStack and EC2.
--
Matthew Miller-- Fedora Project--
omething ready in f21 timeframe is really
> doable in case releng can automate AMIs uploading process. I'll take a
> look at the runner in libtaskotron and existing tasks examples.
Awesome!
--
Matthew Miller-- Fedora Project--
"Tep
ect.org/pub/fedora/linux/updates/20/Images/x86_64/Fedora-x86_64-20-20140407-sda.qcow2
Yes. That is why they were updated.
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
__
ackage ready to get into the distribution proper?
> Don't think so. Look at it as a beta version that I just wanted to throw
> out there. And quite frankly I'm not sure how much time I can spend on
> bugfixes once they come flying in.
Fair enough. Hopefully there will be enough i
, a good answer to the "how do I boot cloud
images locally and get them their ssh keys and userdata?"
> Package for F20: https://copr.fedoraproject.org/coprs/juergh/dwarf/
Is the package ready to get into the distribution proper?
--
Matthew M
e for %license.
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/clou
h probably has other ramifications. But, I did set the SMTP from name to
'Fedora Cloud Trac Tickets' so you could additionally filter on that.
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
_
nit doesn't require cheetah", "NM replaced by
> systemd-networkd", etc. to that, too. And make a link to the
> kernel-split change.
Excellent idea -- +1 to this.
--
Matthew Miller-- Fedora Project--
ake sure to note that in the release
> > notes separately.
> By in place, you mean %packages --excludedocs or something more?
Yeah, again, basically just that. Although we will need the %license change
in order to do this and keep required license files from being left out.
--
u're interested -- I'm just not sure what we
can pull off that will be exciting enough to be a feature.
Or, I dunno, maybe it's worth noting at least, for people making their own
images?
--
Matthew Miller-- Fedora Project--
On Fri, Apr 04, 2014 at 09:31:12AM -0500, Troy Dawson wrote:
> I don't know if anyone else is, but I'm still getting these with the
> weird "To:" address.
> Not that I don't believe you Robyn, but I'm not seeing it.
I changed another thing. Let us know if s
On Thu, Apr 03, 2014 at 05:43:40PM -0400, Matthew Miller wrote:
> Also, talk to Garrett (gholms), the current maintainer and coordinate with
> him.
Because I was just talking to him about this on IRC, I should add. :)
--
Matthew Miller-- Fedora P
s being in the image (and which are likely to significantly increase
the burden of respinning for security updates). Frankie Onuonga was working
on this a little bit. If we can fix that for F21, I'll be happy.
Also, talk to Garrett (gholms), the current maintainer and coordinate with
him.
-
On Thu, Apr 03, 2014 at 02:37:13PM -0400, Matthew Miller wrote:
> https://fedorahosted.org/cloud/query?status=accepted&status=assigned&status=new&status=reopened&summary=^File&milestone=Fedora+21+%28Feature+Deadline%29&order=priority&col=id&col=summary&
ave it all
til then, so -- whatever you can contribute to between now and then =
awewsome.
Thanks everyone!
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud
, I'm all ears!
If you want to filter them out, there is an 'X-Trac-Ticket-ID:' header, by
the way.
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
quot;Something stupid in trac", I'm afraid. I'll figure it out / make sure
someone figures it out.
But, for the record -- filter mailing lists on "List-Id:" to avoid all sorts
of problems along these lines.
--
Matthew Miller-- Fedora Project--
)
Fedora Infrastructure hooked up spamassassin, so that's what we're using
now. We'll see how it goes. :)
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
__
right now is that the
moderation queue so full of spam that looking for legitimately held messages
is the proverbial search for a needle in a haystack. More people just means
more people being annoyed by that. :) By auto-discarding the messages which
are clearly spam, the moderation queue should be s
doesn't get through... that
might be it and I'll look at adjusting the settings.
--
Matthew Miller-- Fedora Project--
"Tepid change for the somewhat better!"
___
cloud mailing
On Wed, Mar 26, 2014 at 06:58:45PM -0400, Matthew Miller wrote:
> And this report
> https://fedorahosted.org/cloud/report/9
> will list the tickets with the meeting keyword
And this one for (future) easyfix items:
https://fedorahosted.org/cloud/report/10
which will hopefully he
ngler (i.e., Joe) some repetative
> > "call for items?" posts.
> +1
And this report
https://fedorahosted.org/cloud/report/9
will list the tickets with the meeting keyword
--
Matthew Miller-- Fedora Project--
___
cl
ust
coordinate, obviously). Otherwise I will when I get a chance, which is
looking to be Friday or Monday.
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listi
w in case of any issues, I'll try to help you!
>
> [1] https://fedoraproject.org/wiki/Releases/21/Schedule
>
- End forwarded message -
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
h
?id=1012952
> There's no way to do a privileged build via index.docker.io so I'm stuck
> at this point. Does anyone have an idea for a fix? :)
As noted, there is supposed to be a fix. Maybe that didn't make it upstr
gt; will work for everyone. How do other projects handle this?
In a zillion different ways. If you prefer to use github for your workflow,
using their tracker seems reasonable for RFEs -- you can create a "wishlist"
label.
--
Matthew Miller mat...@mattdm.org
this wish list?
We don't actually have one yet. :)
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
g a wishlist would probably be good idea. We should ask Scott Collier
where he would prefer to track that -- maybe in the github site, maybe in
our trac, maybe in a wiki.
In any case, I'd personally love to see Cantas. :)
--
Matthew Miller--
n
<https://flock-lmacken.rhcloud.com/proposals#1>
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fed
ngler (i.e., Joe) some repetative
> > "call for items?" posts.
> +1
It may take a week or two of calling for people to add meeting keywords. :)
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedor
On Fri, Mar 21, 2014 at 08:13:07AM -0400, Matthew Miller wrote:
> I am +1 to that. Trac is ugly, but it already has the integration and isn't
> one more service to worry about. If in the future someone wants to set up
> Cantas we can migrate.
Also, I suggest that we start using tr
ne wants to set up
Cantas we can migrate.
I'm going to add some components for the high-level work areas, so tickets
can be categorized.
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
htt
moving it item by item to
<https://fedorahosted.org/cloud/>, that itself might qualify as a (somewhat
boring but practically helpful) easyfix.
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.o
Apparently registration and talk submission is _now_
> <http://flocktofedora.org/>
Who is planning on going? Thinking about giving a talk?
--
Matthew Miller-- Fedora Project--
___
cloud mailing l
g this week,
though, if no one has items.
I hate to lose momentum, but I also hate directionless meetings. :)
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/lis
t; outcome looks like :)
Yeah, I was expecting the system to already have been booted and possibly
initially configured with cloud-init. I think we probably want to solve this
by documenting that we are leaving it enabled and that you should either
turn it off or change what you are feeding to it to
o: ???" indicates that no one has said they are so far.
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
y do that.
> That protection needs to be done in yum/dnf then. I don't see a way
> to do it cleanly in the kernel packages themselves.
Yeah, I agree.
--
Matthew Miller-- Fedora Project--
___
cloud mailing l
rently this is by design in dnf; it's one of the features they didn't
see as valuable. Which is funny to me because that was the case with yum
initially too (we wrote it as a plugin for that reason) but over time it
became a core feature).
--
Matthew Miller-- Fedora Project--
by default, since
> I doubt any of the heat-core personally tested it.
Okay, thanks. I'll look and talk to people too. The other related issue is
whether we want to expose the docker remote API over http; I will talk to
some of the security peopl
rrently
> not on any todo list.
https://fedoraproject.org/wiki/Cloud_Changelist#Change:_Move_to_ImageFactory_For_image_Creation
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedorap
of
> update" magic worked. I know have both kernel-core packages. So I
> figure yum works this magic with any kernel* package.
And this is why I should read all the mail before responding. :)
How about the removal protection?
--
Matthew
s as owners, I think that goes
under the "dependency" section. Have you tested how yum/dnf work with
upgrades (and with yum's feature for protecting the running kernel from
being removed)? Those might need to go in scope and deps too.
--
Matthew Miller-- Fedora Project--
to use its new functionality, we'll want to port it
(both the cron tasks and the kludges in the kickstart) to use the
anaconda/oz/imagecreator-based koji tasks. Hopefully RSN.
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
> perspective of the Cloud SIG?
I think the overall idea is that it is _practically_ abandoned, but not
because anyone wants it to be, just that no one has done anything about it.
It'd be great to see it revived, and as Joe mentioned, it _is_ on our giant
todo list.
--
Matthew Miller
is direction be _workable_ for Heat?
-----------
Thanks!
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo
http://stg.fedoraproject.org/en/using/tutorials/ec2.html
Don't worry about fonts or layout -- this is work in progress. Looking for
feedback on content. Please send that to Robert Mayr (aka robyduck) via irc
or email.
Thanks!
--
Matthew Miller-- Fedora Pr
eplace cloud-init long term for
> the Heat use case. We can't make such changes until Juno wraps up
> (November).
Annnd, just throwing this out there: CoreOS uses a partially-compatibile
cloudinit reimplementation, written, of course, in Go:
https://github.com/coreos/coreos-cloudin
kip it.
Someone then doing a yum install of the driver package on top of the image
would presumably also get the new version and base kernel update.
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
On Tue, Mar 11, 2014 at 08:41:42AM -0400, Matthew Miller wrote:
> Since isn't the only driver for the kernel work you're doing either, I don't
s/Since/Size/
--
Matthew Miller-- Fedora Project--
___
cloud
not an important one.
Since isn't the only driver for the kernel work you're doing either, I don't
think. Another big advantage is that the modularized drivers will allow us
to skip out-of-schedule updates for security updates in the driver package.
--
Matth
f smaller is the
> goal.
Actually, this isn't the case. Fedora Cloud image is actually moderately
smaller than Ubuntu already. We're not even much bigger than CoreOS. Size
isn't the primary driver here. (Although if it were, python is actually one
of the biggest individual th
in-metadata-service up to the level of functionality we need
rather than to try and reforge cloud-init. It may very well be that Heat is
a showstopper in that line of thinking. But in that case, I'd _really_ like
to see an effort around really making cloud-init _ours_.
--
Mat
uld be able to get you access to Fedora's own openstack instance for
working on this -- file a ticket with Fedora Infrastructure, I think.
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedo
On Mon, Mar 10, 2014 at 07:51:42AM +0100, Juerg Haefliger wrote:
> Not yet. As far as I know, this is still held up by fedora legal to
> determine if the HP Cloud customer agreement is acceptable.
Yeah. I'll check back again.
--
Matthew Miller-- Fed
rts? Changes
> need owners.
*nod*
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
ices, install
puppet and hand off, and also whatever Heat needs).
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
tely independently of the work you are
doing here, so there is no additional cost.
--
Matthew Miller-- Fedora Project--
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
401 - 500 of 884 matches
Mail list logo
