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.
On Wed, Mar 16, 2016 at 5:33 PM, Kevin Fenzi <kevin(a)scrye.com> wrote:
> On Tue, 15 Mar 2016 12:51:21 +0100
> Michael J Gruber <mjg(a)fedoraproject.org> 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
> Anyhow, we are still discussing this on the infrastructure list, so
> look for a more detailed and verbose explanation of things once thats
> devel mailing list
devel mailing list