F21 Self Contained Change: Apache Ambari
by Jaroslav Reznik
= Proposed Self Contained Change: Apache Ambari =
https://fedoraproject.org/wiki/Changes/ApacheAmbari
Change owner(s): Peter MacKinnon <pmackinn(a)redhat.com>
Apache Ambari [1] is a cluster management framework and UI for Apache Hadoop.
== Detailed Description ==
The Apache Ambari project is aimed at making Hadoop management simpler by
developing software for provisioning, managing, and monitoring Apache Hadoop
clusters. Ambari provides an intuitive, easy-to-use Hadoop management web UI
backed by its RESTful APIs.
== Scope ==
* Proposal owners: The Ambari [2] package has not yet been accepted into
Fedora. There is an outstanding FPC request [3] for a temporary bundling
exception for Javascript libraries distributed by upstream.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
[1] http://ambari.apache.org/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1076506
[3] https://fedorahosted.org/fpc/ticket/415
10 years
F21 Self Contained Change: Apache Accumulo
by Jaroslav Reznik
= Proposed Self Contained Change: Apache Accumulo =
https://fedoraproject.org/wiki/Changes/ApacheAccumulo
Change owner(s): Christopher Tubbs <ctubbsii(a)apache.org>
The Apache Accumulo [1] is a scalable sorted, distributed, key/value store.
== Detailed Description ==
The Apache Accumulo™ sorted, distributed key/value store is a robust,
scalable, high performance data storage and retrieval system. Apache Accumulo
is based on Google's BigTable design and is built on top of Apache Hadoop,
Zookeeper, and Thrift. Apache Accumulo features a few novel improvements on
the BigTable design in the form of cell-based access control and a server-side
programming mechanism that can modify key/value pairs at various points in the
data management process.
== Scope ==
* Proposal owners: The Accumulo package will provide all the functionality
from the upstream release, packaged for Fedora.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
[1] http://accumulo.apache.org/
10 years
F21 System Wide Change: Anaconda Support for Server Roles
by Jaroslav Reznik
= Proposed System Wide Change: Anaconda Support for Server Roles =
https://fedoraproject.org/wiki/Changes/AnacondaServerRoleSupport
Change owner(s): Stephen Gallagher <sgallagh(a)redhat.com>
Responsible WG: Server WG
The Fedora Server SIG will develop a plug-in for Anaconda to support the
deployment of Fedora Server Roles in kickstart files.
== Detailed Description ==
Deploying Server Roles during installation will require a higher level of
access to the installed system than %post can provide. The Fedora Server SIG
will develop an Anaconda plug-in that will add kickstart directives to deploy
available server roles.
== Scope ==
* Proposal owners: Development work of the Anaconda plug-in.
* Other developers:
** This Change is contingent upon the Server Role Framework [1] being
implemented.
* Release engineering:
** It will be necessary to include this plug-in into the installer image.
* Policies and guidelines: N/A
[1] https://fedoraproject.org/wiki/Changes/FrameworkForServerRoleDeployment
10 years
F21 Self Contained Change: Adopt-Your-Cattle
by Jaroslav Reznik
= Proposed Self Contained Change: Adopt-Your-Cattle =
https://fedoraproject.org/wiki/Changes/Adopt-Your-Cattle
Change owner(s): Matthew Miller <mattdm at fedoraproject>, Stephen Gallagher
<sgallagh at redhat.com >
Responsible WG: Cloud
We provide a smooth path so a Cloud Base Image can be turned into Fedora
Server.
== Detailed Description ==
This is code to be written - it will be a simple script which will take a
generic Fedora Cloud Base Image and turn it into Fedora Server.
== Scope ==
* Proposal owners: Will work with Cloud and Server SIG members to develop the
script and documentation and policies around it.
* Other developers: N/A
* Release engineering: N/A
* Policies and guidelines: N/A
10 years
F21 System Wide Change: (A)Periodic Updates to Images
by Jaroslav Reznik
= Proposed System Wide Change: (A)Periodic Updates to Images =
https://fedoraproject.org/wiki/Changes/%28A%29Periodic_Updates_to_Images
Change owner(s): Cloud WG collectively, with Matthew Miller
<mattdm(a)fedoraproject.org> as point of contact
Responsible WG: Cloud
We want to be able to release updated images not just at release time. Hope
for a one-month regular cadence, plus emergency updates if needed.
== Detailed Description ==
We need to be able to produce official updates to the Fedora Cloud images.
Initially, we plan to release these updates monthly, but also need the ability
to release an out-of-cycle update in the event of a severe security issue.
This involves:
1. policy for level of security issue required for out-of-cycle updates
2. procedure for notification of security updates in images (as with rpm
updates)
3. automated QA (at least smoketests)
4. documentation of QA expectations
5. release engineering process
6. mirroring of updated images
7. updates to web site for new download links and EC2 AMI IDs.
Note that this will apply to the Cloud Base Image, the Docker Host Image, the
Big Data Image, and the Docker Container Base Image. (The latter may need
separate handling.)
Ultimately, we would like to produce updates whenever a package on the image
or the kickstart file for the image changes. This is a step towards that goal.
== Scope ==
* Proposal owners: Create policies and procedures as outlined above. Will also
assist with changes to release engineering.
* Other developers: Contributions welcome!
* Release engineering: Significant impact, obviously. Cloud WG will interact
heavily with Release Engineering and work in concert.
* Policies and guidelines: No changes to existing policies.
10 years
F21 Self Contained Change: Playground repository
by Jaroslav Reznik
= Proposed Self Contained Change: Playground repository =
https://fedoraproject.org/wiki/Changes/Playground_repository
Change owner(s): Marcela Mašláňová <mmaslano(a)redhat.com>, Mirek Suchý
<msuchy(a)redhat.com>
Responsible WG: Env and Stacks WG
The Playground repository gives contributors a place to host packages that are
not up to the standards of the main Fedora repository but may still be useful
to other users. For now the Playground repository contains both packages that
are destined for eventual inclusion into the main Fedora repository and
packages that are never going to make it there. Users of the repository should
be willing to endure a certain amount of instability when using packages from
there.
To avoid any potential confusion, we want to make it clear that the Playground
repository will not host packages that have bad licenses, include proprietary
software or include patented software.
== Detailed Description ==
We are still working on details but the main ideas are finished and described
in the [1].
Packages for the repository are built in COPR. The COPR owner can propose the
repository as a whole for inclusion into the Playground repository by marking
it as such in COPR. Repositories/packages successfully built and satisfying
the Playground repository's Policies are copied into the Playgroud repository.
The one Playground repository includes many Copr repositories.
Playground repository is only meant to provide packages for Fedora 21 and
later versions. Initially, the repository will be provided as a Beta for a
limited number of packagers and testers, so we'll be able to incrementally
define the remaining details of the workings of the repository. To enable the
repository, testers will need to use DNF along with its Copr plugin.
== Scope ==
* Proposal owners:
** Document process, setting, guidelines (if any)
** Communicate with Copr developers
* Other developers:
** Copr devs
*** Ability to mark an individual COPR for inclusion in the Playground
repository.
*** Copr deployment that's considered reliable enough to build packages for
this repo
* Policies and guidelines:
** Packages must follow the Legal Guidelines. In particular, the license for
all packages must be approved in the Legal Guidelines.
** Packages may violate other Fedora Packaging Guidelines.
[1]
https://fedoraproject.org/wiki/Env_and_Stacks/Playground_repository_(draft)
10 years
F21 System Wide Change: Domain Controller Server Role
by Jaroslav Reznik
= Proposed Self Contained Change: Domain Controller Server Role =
https://fedoraproject.org/wiki/Changes/DomainControllerServerRole
Change owner(s): Stephen Gallagher, Simo Sorce -
<server(a)lists.fedoraproject.org>
Responsible WG: Server
The Fedora Server Product will provide a standard deployment mechanism for a
Linux Domain Controller (powered by the FreeIPA project).
== Detailed Description ==
The Fedora Server will be shipped with a role-deployment mechanism. One such
role will be to act as a primary or replica Domain Controller for the Linux
machines in the network.
This will be implemented by taking advantage of the FreeIPA project, packaging
it up within the Server Role Framework and enabling it to be deployed through
the mechanisms described in the Server Role Infrastructure Change Proposal
[1].
== Scope ==
* Proposal owners:
** FreeIPA and the optional CA and DNS components need to be packaged
appropriately for use with the Server Role Infrastructure.
** A D-BUS API plugin needs to be written and tested to support deployment and
monitoring of the Domain Controller Role.
* Other developers:
** None
* Release engineering:
** Pre-loading roles will need to be a capability of the Anaconda install
system, both in the graphical installer and kickstart
* Policies and guidelines:
** Packaging guidelines for this Change should be inherited from the Server
Role Infrastructure Change Proposal.
[1] https://fedoraproject.org/wiki/Changes/FrameworkForServerRoleDeployment
10 years
F21 System Wide Change: Mono 3.4
by Jaroslav Reznik
= Proposed System Wide Change: Mono 3.4 =
https://fedoraproject.org/wiki/Changes/Mono_3.4
Change owner(s): Claudio Rodrigo Pereyra Diaz <elsupergomez(a)fedoraproject.org>
Update the Mono stack in Fedora from 2.10 to 3.4
== Detailed Description ==
Support for Mono versions 3.0 and 2.10 is been discontinued. No further
development of bug fixing is planned for those branches. Mono 3.4 is the
active branch an have many improvements . See upstream notes [1]
== Scope ==
* Proposal owners: Update mono spec and build in koji until is ready.
* Other developers: Some packages may need to be revised, updated or rebuilt,
see Dependencies section
* Release engineering: None
* Policies and guidelines: None
[1] http://www.mono-project.com/Release_Notes_Mono_3.4
10 years
F21 System Wide Change: Database Server Role
by Jaroslav Reznik
= Proposed System Wide Change: Database Server Role =
https://fedoraproject.org/wiki/Changes/DatabaseServerRole
Change owner(s): Kevin Fenzi and Truong Anh Tuan
<server(a)lists.fedoraproject.org>
Responsible WG: Server WG
The Fedora Server Product will provide a standard deployment mechanism for a
Linux Database Server (powered by the postgresql project).
== Detailed Description ==
The Fedora Server Product will be shipped with a role-deployment mechanism.
One such role will be to act as a primary or replica Database Server for the
Linux machines in the network.
This will be implemented by taking advantage of the postgresql project,
packaging it up within the Server Role Framework [1] and enabling it to be
deployed through the mechanisms described in the Framework for Server Role
Deployment Change Proposal.
Note that this role is a secondary target of the Server Working group.
== Scope ==
* Proposal owners:
** Postgresql server and related tools need to be packaged appropriately for
use with the Server Role Infrastructure.
** A D-BUS API plugin needs to be written and tested to support deployment and
monitoring of the Database server.
* Other developers: None
* Release engineering:
** Pre-loading roles will need to be a capability of the Anaconda install
system, both in the graphical installer and kickstart
* Policies and guidelines:
** Packaging guidelines for this Change should be inherited from the Framework
for Server Role Deployment Change Proposal [1].
[1] https://fedoraproject.org/wiki/Changes/FrameworkForServerRoleDeployment
10 years
F21 System Wide Change: Framework for Server Role Deployment
by Jaroslav Reznik
= Proposed System Wide Change: Framework for Server Role Deployment =
https://fedoraproject.org/wiki/Changes/FrameworkForServerRoleDeployment
Change owner(s): Miloslav Trmač <mitr AT volny DOT cz>, Fedora Server Working
Group <server AT lists DOT fedoraproject DOT org >
Responsible WG: Server
A new D-Bus service, and associated command-line tools, to deploy and manage
Server Roles.
== Detailed Description ==
A new D-Bus service will be made available, exposing available server roles,
making it possible to deploy, configure and manage them. Appropriate
functionality will also be exposed as a command-line utility.
== Scope ==
* Proposal owners: Write, document, package and test the D-Bus API.
* Other developers: Possibly use the framework for development of new server
roles.
* Release engineering: Nothing
* Policies and guidelines: Nothing
10 years