[Container-tools] [atomic-devel] Landing pages

[Matt Micene]

>
> I'd like to understand the EC2 strategy a bit more.  Is the goal to have a
> populated / up to date AMI (maybe this exists) that a customer could
> launch?


These already exist and are updated regularly [
https://getfedora.org/cloud/download/atomic.html].  There is an open ticket
b/c some of the currently links were broken.  Clicking on the link for a
particular region is a launch page, so it will trigger an AWS log in.  User
needs an AWS existing account.

Then they essentially hit the OpenShift dashboard and test an app launch.


There is a Test Drive program [https://aws.amazon.com/testdrive/] within
AWS, and RHT does have an OpenShift Enterprise v3 environment there
already.  I work for the company that build the OSE v2 test drive.  Not
sure if the program and expense would be worthwhile for Fedora to take on
for an Origin based test drive.

This does bring up a question of where should any / all of the guides
stop.  Per provider guides should be around installation methods, with a
single "feature tour" for all of them, IMO.  Right now we stop with "Launch
a container", maybe we should move on to "Launch cockpit and do a few
things"?  A tour through the basics atomic command would probably be a good
add.  The Getting Started guide assumes that folks want to set up k8s,
maybe that should be renamed?

- Matt M

On Mon, Feb 1, 2016 at 1:46 PM, Scott Collier <scollier at redhat.com> wrote:

>
>
> On 02/01/2016 10:00 AM, Jonathan Lebon wrote:
>
>> The manageiq website handles this sort of branching pretty nicely:
>>>
>>> http://manageiq.org/download/
>>>
>>> You choose openstack, ovirt, rhev or vsphere, and each heads off
>>> to a nice short quickstart.
>>>
>>
>> Nice, that'd be sweet!
>>
>> So in our case, we'd have
>>
>> - Vagrant
>> - QCOW2 with cloud-init
>> - QCOW2 without cloud-init (i.e. Developer Mode)
>> - EC2
>>
>
> I'd like to understand the EC2 strategy a bit more.  Is the goal to have a
> populated / up to date AMI (maybe this exists) that a customer could
> launch?  There are many details around that, but it would be cool to have a
> process where you take the customers credentials and create the environment
> in AWS that's needed in order to launch this.  Then they essentially hit
> the OpenShift dashboard and test an app launch.
>
> Ansible has part of this:
>
> http://www.ansible.com/tower-trial
>
> It will launch an instance from an AMI that they have listed and you have
> to run through the AWS wizard.  One thing it doesn't give you is "what to
> do next" after launch as a carry over quickstart instruction. It turns out
> that you only need to hit the public DNS name of the instance that was
> launched.  It takes you to a login screen, but you have to figure out what
> the default username / password it.
>
> I'm happy to review this quickstart as needed.
>
>
>
>> I'll whip up a quickstart for devmode.
>>
>>
> --
>
> -Scott
>
> Systems Design and Engineering
>
> Follow Us: https://twitter.com/RedHatRefArch
> Plus Us: https://plus.google.com/u/0/b/114152126783830728030/
> Like Us: https://www.facebook.com/rhrefarch
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/container-tools/attachments/20160201/2827edeb/attachment.htm>