#267: Prepare websites for F21 Alpha release
----------------------+------------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: critical | Milestone:
Component: www.fp.o | Resolution:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
Comment (by mattdm):
Okay, so, here's the picture for cloud deliverables. :)
* We have two major "subproducts"
* '''Fedora Cloud Base'''
* '''Fedora Atomic'''
* Each of these is available either to download in several formats ''or''
to launch in public clouds
* Downloadable Formats
* qcow2 (recommended for OpenStack)
* raw.xz (for other cloud infrastructures -- see wording on current
http://fedoraproject.org/get-fedora#clouds)
* this list is ''unlikely'' to grow
* Public clouds
* Amazon EC2
* That's all for right now but Rackspace and HP Cloud ''should'' be
soon, as well as GCE and possibly others
* What about architectures?
* Fedora Cloud Base is available in two architectures
* 32-bit i386
* 64-bit x86_64
* Fedora Atomic is '''only x86_64'''
* It is likely we will add 64-bit ARM to Cloud Base in future releases
* It is possible that we will drop i386
* Fedora Atomic just plain can't work in i386 because of Docker; this may
change in the future but
it's more likely that we'd add ARM than bother with i386
Sooo, this makes a kind of complicated matrix, and we can present it
multiple ways, but I think fundamentally it makes sense to present it as
"which subproject", then "how do you want it? (download or launch), and
then details like architecture, specific download format, and EC2 region.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:19>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
--
websites mailing list
websites@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/websites
