#163: root user not enabled on vagrant cloud image
-----------------------+--------------------
Reporter: dustymabe | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
-----------------------+--------------------
The password gets set to 'vagrant' here:
https://pagure.io/fedora-
kickstarts/blob/03020f4a748e0616dc3968e2e1afbfd72b33b057/f/fedora-cloud-
base-vagrant.ks#_16
but the root account gets locked because of this line from the base
kickstart:
https://pagure.io/fedora-
kickstarts/blob/03020f4a748e0616dc3968e2e1afbfd72b33b057/f/fedora-cloud-
base.ks#_118
Let's see if we really need that line from the base kickstart anymore and
remove it if not.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/163>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
In order to support the upcoming release of Fedora 24, the Fedora Marketing
team is preparing a press release announcement for next week[1].
While the tone of the article is about where we need it to be, we would
like to solicit input from as many groups as possible for new features that
you feel should have highlighted.
Please visit the discussion area of the release page if you have any
feedback and we will try to include as much as we can.
Thanks,
Brian
[1] https://fedoraproject.org/wiki/F24_general_release_announcement
Brian Proffitt
574-383-9BKP
Twitter: TheTechScribe
Skype: LinuxScribe
www.proffitt.org
Previously (at last year's Flock and after), we've talked about
replacing the Fedora Cloud Edition with Fedora Atomic Edition. (See
previous discussion on this list if you're unfamiliar with this
decision and its rationale.)
We hadn't actually had much movement on _doing_ that, though, so one of
the goals of last week's Cloud WG FAD was to take the next concrete
steps. But, it turned out that everyone in the room (and
teleconferenced in) felt pretty strongly that we actually should go
even further — not just a single container host, but a full container
cluster solution based on OpenShift Origin. So, rather than letting
_that_ linger, let's work on the next steps for _that_.
Roughly, I see that as:
1. Make sure we have agreement from the current Cloud WG members who
couldn't be there. We don't want to make big decisions like this
entirely in a room somewhere without full community input.
2. Reformulate WG members to match new target; possibly some of the
current WG members are more interested in other aspects of cloud
computing, like continuing work on the Cloud Base image. That's
absolutely fine (beyond fine - it's awesome!), but the whole point
of the WG structure is to support the editions.
3. Pick a name! I know, it's bikeshed painting to some degree, but it
really is actually important. Possibilities include:
- Fedora Container Cluster Edition
- Fedora OpenShift Edition
- Fedora Atomic Cluster Edition
- Fedora Some New Entire Name We Create Edition
and all have their plusses and minuses.
4. Update governance documents: that's:
- https://fedoraproject.org/wiki/Cloud/Cloud_PRD
- https://fedoraproject.org/wiki/Cloud/Governance
5. Submit the general idea to the Council for approval to change
Editions (I don't anticipate this being more than a rubber stamp,
but we should definitely get that stamp.)
6. Submit any (probably several) Change requests to FESCo for required
technical changes, and work with Design, Rel-Eng, QA, and etc. on
those.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
The tests are failing for the latest Fedora 23 atomic images:
https://pagure.io/atomic-images/issue/36
There seems to be no rpm db inside the image:
-bash-4.3# rpm -qa
-bash-4.3# echo $?
0
Do we have any system-wide changes we need to propose for F25?
Also, seems weird to have this deadline looming before we even release
F24... :-)
---------- Forwarded message ----------
From: Jan Kurik <jkurik(a)redhat.com>
Date: Tue, Jun 14, 2016 at 2:31 AM
Subject: REMINDER: Submission deadline for System Wide Changes of Fedora 25
in three weeks
To: devel-announce(a)lists.fedoraproject.org, Development discussions related
to Fedora <devel(a)lists.fedoraproject.org>
Hi everyone!
The submission deadline for System Wide Changes of Fedora 25 [1] is
coming pretty soon - in three weeks on July 5th. Alpha release of
Fedora 25 is planned on August 23rd.
Please, submit your System Wide Changes by this deadline, earlier
better. As the deadline applies for System Wide Changes it is always
good to have most of Self Contained Changes proposed as well. In case
you'll need any help with your Change proposals, feel free to contact
me.
Best Regards,
Jan
[1] https://fedoraproject.org/wiki/Releases/25/Schedule
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
--
devel mailing list
devel(a)lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
--
Joe Brockmeier | Community Team, OSAS
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
#162: Milestones, components need updating
---------------------+--------------------
Reporter: jberkus | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
---------------------+--------------------
The components and milestones in this Trac are WAY out of date. The
latest milestone is Fedora 22, and Atomic Host isn't listed as a
component.
How do we update them?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/162>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
HTML Version:
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-06-15/fedora_cloud_…
Full Log:
https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2016-06-15/fedora_cl…
==================================
#fedora-meeting-1: fedora_cloud_wg
==================================
Meeting started by sayan at 17:03:39 UTC. The full logs are
available at https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2016-06-15/fedora_cl…
Meeting summary
--------------------------
* Roll Call (sayan, 17:04:03)
* Action items from last meeting (sayan, 17:10:34)
* scollier to create ticket for migrating docker hub to org (sayan, 17:11:33)
* jzb to follow up on getting fedora cloud images onto Azure and other
providers (sayan, 17:12:30)
* Fedora Cloud FAD (late 2015/early 2016)
https://fedorahosted.org/cloud/ticket/115 (sayan, 17:16:29)
* ACTION: sayan to close the ticket 115 (sayan, 17:19:53)
* Fedora-Dockerfiles examples for Kubernetes
https://fedorahosted.org/cloud/ticket/125 (sayan, 17:20:45)
* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
(sayan, 17:23:21)
* Don't overwrite download location for 2 week atomic images
https://fedorahosted.org/cloud/ticket/147 (sayan, 17:24:48)
* Container "Packager" Guildelines and Naming Conventions
https://fedorahosted.org/cloud/ticket/148 (sayan, 17:31:02)
* Need owner to define basic container smoke testing requirements
https://fedorahosted.org/cloud/ticket/151 (sayan, 17:35:42)
* Fedora Coud Test Day for F24
https://fedorahosted.org/cloud/ticket/152 (sayan, 17:36:59)
* design, deploy and document Fedora OpenShift Playground (FOSP)
https://fedorahosted.org/cloud/ticket/153 (sayan, 17:47:08)
* make Fedora Atomic download page clearer
https://fedorahosted.org/cloud/ticket/154 (sayan, 17:55:55)
* Decide on post-GA update cadence for various deliverables
https://fedorahosted.org/cloud/ticket/155 (sayan, 17:58:32)
* https://public.etherpad-mozilla.org/p/FedoraCloud-WG-FAD-2016
(dustymabe, 18:02:15)
* Need complete Kickstart docs for Atomic Host
https://fedorahosted.org/cloud/ticket/15 (sayan, 18:06:49)
* Open Floor (sayan, 18:07:51)
* ACTION: jzb to follow up on getting fedora cloud images onto Azure
and other providers (dustymabe, 18:14:25)
* ACTION: jzb take another run at legal on azure cloud issue
(dustymabe, 18:14:34)
Meeting ended at 18:15:01 UTC.
Action items
------------------
* sayan to close the ticket 115
* jzb to follow up on getting fedora cloud images onto Azure and other providers
* jzb take another run at legal on azure cloud issue
Action items, by person
----------------------------------
* jzb
* jzb to follow up on getting fedora cloud images onto Azure and
other providers
* jzb take another run at legal on azure cloud issue
* sayan
* sayan to close the ticket 115
People present (lines said)
---------------------------------------
* dustymabe (96)
* sayan (64)
* jzb (26)
* maxamillion (22)
* zodbot (21)
* rtnpro (12)
* jberkus (10)
* scollier (9)
* tflink (8)
* coremodule (7)
* sjennings (4)
* bowlofeggs (3)
* gholms (1)
--
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B
Proud to work at The Open Organization!
#115: Fedora Cloud FAD (late 2015/early 2016)
-----------------------+-----------------------
Reporter: dustymabe | Owner: dustymabe
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Planning | Keywords: meeting
-----------------------+-----------------------
At Flock we talked about having a Fedora Activity Day for the cloud
working group to get some work done. This ticket will serve as a stub for
planning and coordination of this event.
The first step is to write up a proposal and submit it for review.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/115>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System