SLA of Copr and changes in future

[Miroslav Suchý]

We are discussing in Fedora Infrastructure about level of SLA of some
services. And mainly because of Copr. There are some other services e.g.
Jenkins, Taiga. However Copr is probably most popular. Copr service was
from begging meant as somehow beta version and did not pass all the
requirements Fedora Infrastructure team has for Fedora services.

So rather later than never - I would like to emphasize:

 Copr is experimental service provided as a courtesy for the
 community.  There is no expectation of a SLA and the service may be
 changed from time to time as part of its further development.

This is the reason why Copr changed hostname recently. From
copr.fedoraproject.org to copr.fedorainfracloud.org.
There is ongoing discussion on Fedora Infrastructure mailing list, that
only fully supported services should remain in fedoraproject.org domain.
All experimental services should be moved to fedorainfracloud.org.
Recently there was suggestion to use http://fedoracommunity.org/. So it
is not settled down and the resolution may change in near future.

Copr team works hard to become fully supported service in future and
re-appear again as copr.fedoraproject.org. This will not be painless.
Beside a lot of work for my team, it will mean rebuilding of all
packages. We will provide tool which will easy the migration for you.
However I have no precise ETA when we met all Fedora Infrastructure
requirements.

In the mean time, it was announced on copr-devel list that the redirect
from copr.fedoraproject.org will be discontinued on Tuesday 22nd March.

Miroslav Suchý

[Michael J Gruber]

Miroslav Suchy venit, vidit, dixit 14.03.2016 23:01:
>  There is ongoing discussion on Fedora Infrastructure mailing list,
> that
>  only fully supported services should remain in fedoraproject.org domain.
>  All experimental services should be moved to fedorainfracloud.org.
>  Recently there was suggestion to use http://fedoracommunity.org/. So it
>  is not settled down and the resolution may change in near future. 
Going just by the names, I would expect "fedorainfracloud" to be the
fedora infrastructure in the cloud, i.e. the infrastructure services
that fedora relies on; and "fedoraproject" to be project work in
progress. Just the other way round compared to the plan.

Michael

[Kevin Fenzi]

On Tue, 15 Mar 2016 12:51:21 +0100
Michael J Gruber <mjg(a)fedoraproject.org&gt; wrote:

>  Miroslav Suchy venit, vidit, dixit 14.03.2016 23:01:
>  > There is ongoing discussion on Fedora Infrastructure mailing list,
>  > that only fully supported services should remain in
>  > fedoraproject.org domain. All experimental services should be moved
>  > to fedorainfracloud.org. Recently there was suggestion to use
>  > http://fedoracommunity.org/. So it is not settled down and the
>  > resolution may change in near future.  
>  
>  Going just by the names, I would expect "fedorainfracloud" to be the
>  fedora infrastructure in the cloud, i.e. the infrastructure services
>  that fedora relies on; and "fedoraproject" to be project work in
>  progress. Just the other way round compared to the plan. 
Well, our cloud isn't setup with HA currently and is running a older
version of openstack, so it's not something we consider as solid as all
the normal virtual hosts running vm's for applications (and in most
cases in HA). We are working to upgrade it, but until we have things in
place it's just not as reliable as our regular infrastructure.
Additionally, things in our cloud are mostly development instances,
test machines, proof of concept, etc... ie, things that aren't really
supported. 

Anyhow, we are still discussing this on the infrastructure list, so
look for a more detailed and verbose explanation of things once thats
complete. 

kevin

[Michal Novotny]

I must agree that "fedorainfracloud" also sounds to me like the more stable
variant out of the two (without any previous historical knowledge).

clime

On Wed, Mar 16, 2016 at 5:33 PM, Kevin Fenzi <kevin(a)scrye.com&gt; wrote:

>  On Tue, 15 Mar 2016 12:51:21 +0100
>  Michael J Gruber <mjg(a)fedoraproject.org&gt; wrote:
>
>  > Miroslav Suchy venit, vidit, dixit 14.03.2016 23:01:
>  > > There is ongoing discussion on Fedora Infrastructure mailing list,
>  > > that only fully supported services should remain in
>  > > fedoraproject.org domain. All experimental services should be moved
>  > > to fedorainfracloud.org. Recently there was suggestion to use
>  > > http://fedoracommunity.org/. So it is not settled down and the
>  > > resolution may change in near future.
>  >
>  > Going just by the names, I would expect "fedorainfracloud" to be the
>  > fedora infrastructure in the cloud, i.e. the infrastructure services
>  > that fedora relies on; and "fedoraproject" to be project work in
>  > progress. Just the other way round compared to the plan.
>
>  Well, our cloud isn't setup with HA currently and is running a older
>  version of openstack, so it's not something we consider as solid as all
>  the normal virtual hosts running vm's for applications (and in most
>  cases in HA). We are working to upgrade it, but until we have things in
>  place it's just not as reliable as our regular infrastructure.
>  Additionally, things in our cloud are mostly development instances,
>  test machines, proof of concept, etc... ie, things that aren't really
>  supported.
>
>  Anyhow, we are still discussing this on the infrastructure list, so
>  look for a more detailed and verbose explanation of things once thats
>  complete.
>
>  kevin
>
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  http://lists.fedoraproject.org/admin/lists/[e-mail]
>
>

[Stephen John Smoogen]

On 16 March 2016 at 12:42, Michal Novotny <clime(a)redhat.com&gt; wrote:
>  I must agree that "fedorainfracloud" also sounds to me like
> the more stable
>  variant out of the two (without any previous historical knowledge).
>  
Like all bikesheds.. we went through a lot of different names to try
and convey that this was experimental but trying to make it short and
clear was not possible.. also my alternative of
"fedoraprojects-use-at-your-own-risk-cloud.org" was vetoed.


>  clime
>
>  On Wed, Mar 16, 2016 at 5:33 PM, Kevin Fenzi <kevin(a)scrye.com&gt; wrote:
> >
> > On Tue, 15 Mar 2016 12:51:21 +0100
> > Michael J Gruber <mjg(a)fedoraproject.org&gt; wrote:
> >
> > > Miroslav Suchy venit, vidit, dixit 14.03.2016 23:01:
> > > > There is ongoing discussion on Fedora Infrastructure mailing list,
> > > > that only fully supported services should remain in
> > > > fedoraproject.org domain. All experimental services should be moved
> > > > to fedorainfracloud.org. Recently there was suggestion to use
> > > > http://fedoracommunity.org/. So it is not settled down and the
> > > > resolution may change in near future.
> > >
> > > Going just by the names, I would expect "fedorainfracloud" to be the
> > > fedora infrastructure in the cloud, i.e. the infrastructure services
> > > that fedora relies on; and "fedoraproject" to be project work in
> > > progress. Just the other way round compared to the plan.
> >
> > Well, our cloud isn't setup with HA currently and is running a older
> > version of openstack, so it's not something we consider as solid as all
> > the normal virtual hosts running vm's for applications (and in most
> > cases in HA). We are working to upgrade it, but until we have things in
> > place it's just not as reliable as our regular infrastructure.
> > Additionally, things in our cloud are mostly development instances,
> > test machines, proof of concept, etc... ie, things that aren't really
> > supported.
> >
> > Anyhow, we are still discussing this on the infrastructure list, so
> > look for a more detailed and verbose explanation of things once thats
> > complete.
> >
> > kevin
> >
> > --
> > devel mailing list
> > devel(a)lists.fedoraproject.org
> > http://lists.fedoraproject.org/admin/lists/[e-mail]
> >
>
>
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  http://lists.fedoraproject.org/admin/lists/[e-mail]
>  


-- 
Stephen J Smoogen.