d, which is a big
win in runtime memory use.
--
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
On Thu, Mar 19, 2015 at 03:54:24PM -0400, Joe Brockmeier wrote:
> I think Matthew Miller said he added the kickstart file, need to see
> what else needs to be done there.
Someone needs to test that it works, and make any needed changes.
That someone _might_ be me, but if we want it befor
On Thu, Mar 19, 2015 at 04:19:33PM -0600, Derek Carter wrote:
> >On Thu, Mar 19, 2015 at 03:54:24PM -0400, Joe Brockmeier wrote:
> >>I think Matthew Miller said he added the kickstart file, need to see
> >>what else needs to be done there.
> >Someone needs to te
On Thu, Mar 19, 2015 at 08:41:55PM -0400, Matthew Miller wrote:
> > >>I think Matthew Miller said he added the kickstart file, need to see
> > >>what else needs to be done there.
> > >Someone needs to test that it works, and make any needed changes.
> > Sen
ins overrode
> the upstream default, there'd only be one).
I won't speak for everyone, but I *think* the general cloud attitude
here is to use private/public keys and certificate-based auth instead of
passwords in any case.
--
Matthew Miller
Fedora Project Leader
_
rather than some other Linux base?
--
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
it a lack of someone to make and test the needed changes?
--
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
anything
> in Microsoft support forums.
I don't know about Microsoft, but Atomic aims to be a lot more than
just a "boot to docker" platform, including application orchestration.
--
Matthew Miller
Fedora Project Leader
___
cloud
ll continue to be.
--
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
and forth as appropriate without much
hassle). And of course, with my employer's hat on, if you want
certification and support, RHEL Atomic is always there for you (on a
still fast but even more conservative cycle).
--
Matthew Miller
Fedora Project Leader
__
on on that issue?
Yep, fair enough -- sorry for thread hijack. :)
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fed
On Mon, Mar 30, 2015 at 10:54:24PM +0530, Kushal Das wrote:
> The latest nightly build[1] passed through Tunir, without the missing
> eth0 issue[2].
> [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=9359447
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1204612
Nice!
--
Ma
es, I can test them today.
Did anyone get a chance to do anything here? I know last week was a
busy week.
--
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
nks for the update.
--
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
the edition-specific Anaconda to include most of that
configuration is a future work item (that I don't think anyone is
working on actively)
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.
ase?
--
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
of the planned
every-two-week releases, and as "graduating" from the cloud umbrella,
or about its at-F22 state and as a Cloud SIG/WG output?
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https:
tty nifty, and I think fits with our overall
Fedora-for-developers story. Because as much as we'd like to get all
software devs running Fedora on their desktops, a lot, lot more are
running Windows. So, whichever way we can get in, we should.
--
Matthew Miller
Fedora Project Leader
__
; https://fedorahosted.org/cloud/ticket/84.
Good call.
--
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
hat I'm
focused on. I need a good story. :)
--
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
different thing compared to the other types of projects the
> trademark guidelines are addressing.
Agreed!
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinf
> opportunity to use a Fedora-based Atomic Host and gives our developers
> the ability to move fast and break things if needed."
That works for me. Any volunteers for actually working on making
http://atomic.fedoraproject.org/?
--
Matthew Miller
Fedora Project Leader
_
is
updated-every-two-weeks Fedora Atomic to its slower-moving downstreams,
but as I understand the plan, on a _much_ faster timeframe. So, it's
great to be involved at both levels.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
c
lower-moving than a full
> release every two weeks. A full release every Fedora release is ideal
> but since that's been ruled out, the next best thing is a CentOS
> Atomic that tracks RHEL Atomic.
It's not completely ruled out; we're just not feeling ready for it y
r/). This could either be blocks on
the right-side bar, or horizontal stripey panels in keeping with the
new design.
If this sounds good to people, I can start the conversation with the
web team. The initial Atomic page will probably look basically like the
Dock
d/download/
> > could become a little less maze-like.
> I'm in favor; who can help make this happen?
I think it's mostly the web team... maybe design. Everything _behind_
that basically stays the same.
--
Matthew Miller
Fedora Project Leader
_
On Fri, Apr 17, 2015 at 02:45:25AM -0400, Joe Brockmeier wrote:
> Did I miss something, or when did we decide to add "screen"? IIRC that
> was discussed and rejected, as we already provide tmux.
+1 to just tmux
--
Matthew Miller
Fedor
needing cloud-init or grubby. For host images, I think the best
approach might be to make a minimal python package (possibly a parallel
one rather than splitting the existing one) with _just_ the modules
installed needed to run those programs. Right now, IDLE and 2to3 a
significant portion of the pyt
dl.fedoraproject.org/pub/alt/stage/22_TC1/Docker/x86_64/.
> > 1. Will there be newer media by Test Day?
> I think for now those are the latest pieces of media we are going to
> use.
FWIW, there's a TC2 Docker
https://dl.fedoraproject.org/pub/alt/stage/22_TC2/Docker/x86_64/
lking points when they're at events (etc.), and for
> anybody who's talking to press about the F22 release.
Hey everyone! Any progress / ideas for this? The cloud section needs
some help!
--
Matthew Miller
Fedora Project Leader
___
e a blocker since atomic is nonblocking.)
--
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
so it can be proposed as
> a freezeexception?
Yes -- otherwise it won't get included in the composes and will be
shipped as a zero-day update.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fed
I know these are in fedmsg somewhere or something, but for testers'
convenience, what are the AMI ids for RC2?
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/ma
loud-Base-22-20150521 for (pending) RC3...
--
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
of
>the world
... making this less embarrassing by using to emphasize the two-week
images coming up. And then actually figuring out how to make that
happen and do it.
--
Matthew Miller
Fedora Project Leader
___
cloud maili
Let's figure out how to give ourselves this option in the future.
--
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
or hold older Docker version for some reasons. (Up for
discussion — that's why this is in phase 3!)
11. More what else?
Does this seem basically sane and in line with what people are
expecting? What's missing? What's extra? What's just wrong? :)
-
ld be good. making rawhide more of a place to be, for
> me should be our goal. get the new awesome things in there and used
> by people, leave the stable releases stable
The concern I'm hearing is that rawhide is hard to develop on, because
parts other than what you're working on
s conversation go a couple of
rounds and then (after the F22 release and associated everything calms
down) drawing some diagrams seems like a great idea.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedo
fundamental update model, unless the updates you
need are built in, you have to have an update+reboot built into the
deployment cycle. I think, really, the NFS thing is just an example --
the two-week updates are going to be important.
--
Matthew Mille
rticular had moved far from its
> original PRD). We decided to keep that plan and adjust the future.
And, yeah, it's really too late to be putting more demands on this
year's Flock.
--
Matthew Miller
Fedora Project Leader
_
on stack from the cloud image.* Having a better
We need to talk to Peter Jones about plans to rewrite grubby in Python.
I'm very sympathetic to his wish to have it no longer be in C, but if
we _really_ are moving to getting python out
--
Matthew Miller
Fedora Project Leader
__
ar the reasoning
> behind it.
I think because it's one of the biggest and most complex things in
minimal.
--
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
oesn't exist today.
But in order to be really useful unless they're all-in on Fedora, many
people will want the python version for their
infrastructure/environment, not whichever python we happen to ship in a
given release.
--
Matthew Miller
Fedora Project Leader
ffer a very
lightweight image — minimal + provisioning utils like cloud-init —
and then language stacks via SCLs. Adding those was where the utility
was supposed to come from.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lis
tp://koji.fedoraproject.org/koji/taskinfo?taskID=9832786
--
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
ht include various
ansible-ready or puppet-ready images, possibly with other tools
installed as fits the use case.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/l
t in Cloud, I'd rather see an image that
> is flexible with utilities for people to customize and build on top of
> even if that means it isn't the tiniest, thinnest image out there.
Oh, it won't be. The tiniest, thinnest images are in the 10MB range.
--
Matthew Miller
Fedor
x27;t think too much
choice is a problem here. See for example the success of
<https://bitnami.com/stacks>, which is a similar idea. And churn --
well, we have other initiatives aimed at modulating that.
--
Matthew Miller
Fedora Project Leader
_
he fly for someone to download. That seems a
Sure -- that's one of the approaches we've discussed.
> > well, we have other initiatives aimed at modulating that.
> Such as?
Such as the modularization effort we just approved in the council?
--
Matthew Miller
Fedora Project Lea
n
Fedora". But it sounds like you mean "cloud computing world overall
changing really fast"?
--
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
nts. You might be the right person to talk to about
figuring out if we can do anything about this.
--
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
rgely,
addressing the more traditional server model, where each machine serves
a unique purposes and is carefully maintained. Fedora Cloud is
addressing the emerging cloud computing world, and provides a base for
deploying scale-out applications.
--
Matthew Mil
eat or EC2 console)
> slightly faster isn't an advantage if I then lose more time installing
> packages over the network, creating a new image to then start using as my
> baseline.
Agreed — that's where the idea of having a dozen or so images
preconfigured with popular runtimes m
On Thu, Jun 11, 2015 at 04:48:37PM -0400, Matthew Miller wrote:
> Agreed — that's where the idea of having a dozen or so images
> preconfigured with popular runtimes makes sense. But an image with
> _all_ the runtimes doesn't.
And that said: if we _do_ decide to make Fedora
On Fri, Jun 12, 2015 at 11:11:51AM -0400, Joe Brockmeier wrote:
> I, for one, care a lot - but have been buried. Sorry.
Yeah, ditto. There was this whole F22 release thing that happened. :)
--
Matthew Miller
Fedora Project Leader
___
cloud mail
's own product then it should exist slightly differently such that
> it has it's own set of koji tags, inherits from $current, but
> subplants the components it needs. This would however be a massive
> shift because as it turns out that is something that's
> make the rework we did in f22 pointless and wasted and we've already
> had that discussion.)
H -- what about making linux-firmware a Requires(Pre) for
kernel-modules instead of kernel-core?
--
Matthew Miller
Fedora Project Leader
___
r layered
images" issue — that wasn't on _this_ list but perhaps needs to be.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fe
ens I think
> you get a warning anytime you use yum/dnf.
In this case, since it's only a Requires(pre), RPM doesn't mind.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedora
transaction.
It'd be nice to avoid the network traffic.
I'm assuming here that the kernel update itself will act gracefully if
the package isn't there. That's not actually a tested assumption. :)
--
Matthew Miller
Fedora Project Leader
___
e.
If people here think something else would be better, that's fine with
me!)
--
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
s failing in the image build
process. I don't remember the current state.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of
On Tue, Jun 16, 2015 at 07:46:14PM -0400, Matthew Miller wrote:
> https://fedoraproject.org/wiki/Changes/Two_Week_Atomic
Now updated based on some feedback and with a schematic of how I
envision the build→test→release→present process working. If anything in
that looks wrong, let's fix i
next step specifically
listed as out of scope for the change itself.
<https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service>
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https:
I
know that Docker changed "trusted" to "automated", because they're not
actually offering any claim to trust through this feature.
Is there a way we could structure it differently to get any similar
benefit?
--
Matthew Miller
Fedora Project Leader
nto various components — or in fact
could be the basis of an initial immediate set. What do you think?
Another thing of note: we could talk with Infrastructure about adding
Pagure support to all the new dist-git repos, so they'd all have a web
based
now's
the time to think about it, since it seems likely that we want a
separate namespace anyway.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/c
. Removing Python from that image would be a serious curveball
> since most people expect to have Python available on any system
> running yum/dnf.
Yeah, I'm willing to back down on wanting to remove Python.
--
Matthew Miller
Fedora Project Leader
_
those to Amazon, etc., and this could serve as the generic
building-block cloud image people want. It'd probably be bigger, but
that's okay because we'd know _why_. (And I hope with the improvements
we're making on size in general
On Fri, Jul 10, 2015 at 02:30:43PM -0400, Matt Micene wrote:
> So we are currently the smallest uploaded AMI and consuming the least
> amount of available space in base, current version, community AMIs.
Now there's a quote. :)
--
Matthew Miller
Fedora Pro
mic" Workstation, with "Atomic" in quotes - unless
there's a lot of change in both projects, think it'd be more confusing
than not to actually call it that.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@list
g akin to dist-git for dockerfiles (part
of https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service),
this makes perfect sense.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.
there be something about GCC in this set of talking points?
Yes. :)
--
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
On Tue, Aug 04, 2015 at 01:49:57PM +0200, Gabriele Trombini wrote:
> Hi all,
> as usual marketing team drafted the talking points page [1].
This is great — thanks!
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
eah grab me if possible. :)
--
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
ml
> > Could we please have your(cloud-WG) consent to enable this feature on the
> > Fedora
> > cloud variant?
> Hello...!?!
Many people are at Flock this week. Please have patience.
--
Matthew Miller
Fedora Project Leader
___
cloud
ng about this thread. :)
--
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
loud Base Image, and list their
names somewhere.
--
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
ot;Other Downloads" section of
<https://getfedora.org/en/cloud/download/>, introduced like this:
"Looking for a plain, non-Atomic image optimized for cloud
environments? Download Fedora Cloud Base Image: [...]"
--
Matthew Miller
Fedora Project Leader
__
ply: each download may correspond to one
instantiation to try it out, or none at all, or a million.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora C
On Wed, Aug 19, 2015 at 02:59:00PM -0400, Matthew Miller wrote:
> qcow2 downloads are roughly half-and-half. I don't have stats for
> ec2-click-to-launch (because I forgot to ask for them.) And, the
This is averaging a little more than 10 a day, combined base and
atomic. That's af
info like kernel version, docker version, kubernetes, version etc.
*nod* That sounds great.
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedo
selecting cloud as a target focus in the first place, I think this is
a good move. But let's do the process. :)
(Apologies if this was already discussed in IRC or somewhere... I
didn't see any mail about it so I figured I'd kick this off.)
--
Ma
roach would be to outline the testing level for each
image type in the paragraph right above the download (or launch) link.
But that seems like it might be too much text.
What do you think?
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
On Thu, Sep 10, 2015 at 11:38:24AM -0500, Zack Cylinder wrote:
> Alkjsadflkajdflkasjfalsjfaefjwlak
Zack, cat got your keyboard?
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
ht
he
> automated pipeline is churning out in the Fedora 24 time frame but for
> now this is probably best.
My hope is that in that time frame, we can make it simple for
contributors to add tests — that's an easy way to make a meaningful
contribution.
--
Matthew Miller
Fedora Project Leader
__
On Thu, Sep 10, 2015 at 01:02:10PM -0400, Matthew Miller wrote:
> * Vagrant boxes:
> - same tunir-based test suite in VM environemnt
Followup! Kushal points out that we are testing the KVM vagrant images
in this way, but not testing VirtualBox. (Because we don't have
VirtualBox i
didate
vagrant images every two weeks. That doesn't seem very sustainable,
though. And, kind of by design, it's likely that the images published
will be the ones from the very night before, allowing for a very short
window for that kind of testing
t/108
With the decision to focus on atomic, we actually have a _lot_ to do
here.....
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code o
t?
I was kind of thinking it _would_ take effect for Fedora 23, but if
the Atomic team + releng + cloud WG don't think it's ready, then I
guess that's easy. :)
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedor
).
Feedback? I think it looks great.
--
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
a little ahead of myself in excitement
-- if not everyone is down with this plan, let's figure out what it
*should* look like. I hope I'm not actually too far off and that all of
the above makes sense.
--
Matthew Miller
Fedora Project Leader
tory. So, some 80%
of my enthusiasm for Fedora Atomic comes simply because it *does* fit
that picture so well. (That I also think it's a major step in OS
evolution is just... icing on the cake.)
--
Matthew Miller
Fedora Project Leader
___
cloud mai
On Tue, Sep 15, 2015 at 04:20:36PM -0400, Matthew Miller wrote:
> All that said, I may be getting a little ahead of myself in excitement
> -- if not everyone is down with this plan, let's figure out what it
> *should* look like. I hope I'm not actually too far off and that all o
On Tue, Sep 15, 2015 at 06:45:14PM -0700, Garrett Holmstrom wrote:
> On 2015-09-15 11:23, Matthew Miller wrote:
> >https://mattdm.fedorapeople.org/misc/newfedoratomiclogomockup.png
> I think it looks great! Do we have permission from the Project
> Atomic folks to use their logo
launch page to include guest images for _all_ of the editions
and spins which make sense -- cloud base, server, and even xfce (I saw
a great demo of this running remotely via x2go at Flock). Again see
https://arm.fedoraproject.org/ as a model.
--
Matthew Miller
Fedora
om your
point of view? (For reference, the Alpha annoucement is
https://fedoraproject.org/wiki/F23_Alpha_release_announcement.) it's
fine, but not super-exciting. Can we do better?
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@li
mages
from the general gold compose ("traditional")
Plan B: at F23 release, use the images from the traditional compose.
Switch to Two-Week images two weeks later.
Colin says that the Atomic dev team is good with switching to F23 as
the base at F23 release -- no known need to lag.
--
nal polish for the Tuesday announcement.
Cloud WG -- still need some more there, though!
--
Matthew Miller
Fedora Project Leader
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code
601 - 700 of 884 matches
Mail list logo