On Fri, Aug 26, 2016 at 8:36 AM, Stephen John Smoogen <smooge(a)gmail.com> wrote:
On 26 August 2016 at 09:51, Stephen Gallagher
<sgallagh(a)redhat.com> wrote:
> On 08/25/2016 01:34 PM, Matthew Miller wrote:
>>
>> We've talked about this for a while, but let's make it formal. The plan
>> is to transition from Cloud as a Fedora Edition to Something Container
>> Clustery (see
https://fedoraproject.org/wiki/Objectives/ProjectFAO).
>>
>> But, we still need cloud as a _deploy target_. The FAO-container-thing
>> will continue to have cloud image deploy targets (as well as bare
>> metal). I think it makes sense to _also_ have Fedora Server as a cloud
>> deploy target.
>>
>> This could possibly be both a Fedora Server Minimal Cloud Image and
>> Fedora Server Batteries Included Image — but that'd be up to Server WG,
>> I think.
>
>
> I've been socializing this a bit lately (at Flock, on #fedora-devel, etc.) and I
> think it makes a lot of sense to unify the cloud image into Fedora Server. I'm
> not sure we necessarily want to try to produce two different images here,
> though. I think we probably want a single cloud image that is just Fedora Server
> (as it would be installed by Anaconda) plus whatever "cloudy bits" are
needed to
> get it up and running.
>
> The Server and Cloud Editions previously didn't differ in too many ways except
> for the inclusion of rolekit and Cockpit in the Server. With our plans to remove
> rolekit in favor of a config-management system like Ansible, I think that really
> only leaves Cockpit (and its dependencies) as a possible point of contention.
> Cockpit's modularity does mean that we can minimize its footprint if we opt to
> skip things like the NetworkManager and storaged support from the Cloud image.
>
> We can debate this later, but for now I'd be in favor of just keeping all of
> Cockpit there and available, if only because it helps us strongly encourage the
> use of the modern APIs that it uses under the hood (such as NetworkManager and
> storaged).
>
I expect there will need to be 2 images.. mainly because people always
ask for a 'minimal' image with nothing but a ssh, shell and dnf in it.
(actually they say they want even less than that... but rarely show up
to do the work on getting that working.)
Just for a size perspective:
Fedora-Cloud-Base-25_Alpha-2.x86_64.qcow2 232M
Fedora-Cloud-Base-24-1.2.x86_64.qcow2 195M
That uses cloud-init which Server WG may want to drop, the Cloud WG
was looking at using something else eventually. Since Cockpit from
Fedora 24 has a way to install ssh public keys, it could be this image
requires public key authentication by default (or maybe all Server
images can do this now?) and use Cockpit to install the keys.
I guess the nice thing about cloud-init is that cloud instances can be
provisioned pretty easily by having an ISO "sidecar" file attached to
the VM's cdrom device, without having to login to that VM to set that
up. I don't know if that's something Cockpit can mimic, a way to
produce an export-import file?
--
Chris Murphy