Ticket #4765 (RFR) - Domain name request for the Fedora Bootstrap project web server
kevin at scrye.com
Mon Jun 1 11:45:08 UTC 2015
On Fri, 29 May 2015 09:15:39 -0400 (EDT)
Jaromir Capik <jcapik at redhat.com> wrote:
> Hello Kevin.
> > > We created a homepage for the Fedora Bootstrap project we're
> > > hosting on the OS1 cloud VM and we'd like to request a well
> > > looking domain name for the web URL.
> > Well, there's some issues there in my mind I'm afraid. :(
> > Fedora Infrastructure has permissions to brand/call things using the
> > Fedora trademark, granted by the Fedora Board (Now Fedora Council).
> > However, you are running this service, not us, so I am not sure we
> > can put it in the fedoraproject.org domain. Additionally, people
> > will see 'fedoraproject.org' and come to us about it and we will
> > have no idea how to manage or fix it.
> > > We believe the 'bootstrap.fedoraproject.org' is
> > > the most suitable and easy to remember name. The current FQDN is
> > > vm-107-179-132-209.osop.rhcloud.com (pointing at 184.108.40.206)
> > > and we've requested a change to fedora-bootstrap.osop.rhcloud.com
> > > in the OS1 tracker (should be configured tonight) so that you
> > > could create a CNAME record if needed. We expect the server could
> > > be under a heavy network load soon as it offers rootfs snapshots
> > > and therefore it isn't wise to do proxying. Please, let me know
> > > if you need any additional data.
> > Yes, I would. ;)
> > In addition to the trademark stuff:
> > * This looks neat! I think it will be a great help for bringing up
> > new arches and possibly also letting us do better mass rebuilds.
> > * Is there some place we can see the code ?
> I've put the link to the main page. However, the page still
> requires tweaks. We've created a request for authorized project
> logo that needs to be in place prior making the page public.
Just as a side note there's another popular project using that name
Might be confusing to some folks.
> > * How far along are you? I see there's 6 stages listed on the web
> > page...
> We currently have scripts for the first 4 stages, but the testsuite
> only supports the first stage at the moment. The rest stages will be
> implemented continually.
> > * I see koji listed there, is that the fedora koji? Or your own?
> > Or ?
> We plan to run our own testing koji hub, but we're not there yet.
> The most difficult thing is to find a suitable hardware and sufficient
> storage space for rootfs snapshots in order to provide maintainers
> with pre-built environments, etc. Our requirements are 'huge' and
> I'm happy I was able to find acceptable builders for all the listed
> architectures. We're still waiting for NFS storage for the s390
> builder and the cloud storage has only 200 GB for the snapshots. But,
> better than nothing. Step by step.
> > * There might be some overlap here with the koschei project. It only
> > does scratch builds however, and you likely need buildroots, but
> > there could be a lot of the koschei logic re-used especially if
> > this is a koji interfacing project.
> I'm aware of the koschei project and keeping it in mind.
ok. Just wanted to mention it.
> > * Are you planning on continuing to host it where it is, or is the
> > idea that it would be something we would want to run in fedora
> > infrastructure?
> I'm not against running it anywhere if it suits our needs.
> > I'm sure there will be other questions, but thats a good start. ;)
> Sure. Don't hesitate to ask.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the infrastructure