On 03/10/2014 04:32 PM, Sandro "red" Mathys wrote:
Just noticed that removing Python would obviously also mean no
heat-cfntools. Do we want to accept that (if we go with remove-python
at all)?
Starting to wonder a bit how users are supposed to use Docker. What
other mechanisms do we have to actually run a container with Docker
once the image is deployed?
removing cloud-init, heat-cfntools, and the new TripleO related tools
os-collect-config, os-apply-config and os-refresh-config may make sense
for a *host* operating system, which I believe Atomic is targeting.
If these are removed from a guest operating system, the guest won't be
able to function with TripleO, Heat, or anyone that depends on
cloud-init. Removing cloud-init support effectively kills any
motivation for AWS adoption of a guest operating system that we may produce.
I am a bit confused at the scope because min-metadata-server was
mentioned early on, but is unnecessary if the target of this OS is to
only run on hosts.
Ideally a python run time would still be available to run virtualization
platforms like OpenStack. Such a bare-bones operating system would make
alot of sense, but I've copied a TripleO upstream developer (James) for
his thoughts on atomic + ostree and its relationship to how TripleO
handles continuous deployment through imaging.
Regards,
-steve
On Mon, Mar 10, 2014 at 8:21 AM, Colin Walters <walters@xxxxxxxxxx> wrote:
- How does one activate the deployed product if extlinux is the active
bootloader? The website has only instructions for GRUB (bls_import, etc).
Ah, you probably hit this:
https://bugzilla.gnome.org/show_bug.cgi?id=726007
Probably this, will try a workaround later. Thanks.
This is also related:
https://bugzilla.gnome.org/show_bug.cgi?id=722845
Basically to make ostree drive extlinux, the layout needs to look like this:
https://github.com/cgwalters/rpm-ostree/blob/master/src/autobuilder/js/libqa.js#L359
- How does one get rid of the 'traditional Fedora' once the product is
active?
Maybe something like:
rpm -qal | while read line; do rm $line || rmdir $line; done
rpm -qal | while read line; do rm $line || rmdir $line; done
I'm pretty sure that's not a good way to go. Not sure if there's any
much better. We'll see once I had time to play around some more.
...figure both won't be necessary anymore once we can use Anaconda to
install a product directly, but in the meantime it would be helpful for some
testing and more generally help my understanding. :)
Yep, Anaconda support will fix both.
Great, looking forward to that.
-- Sandro
_______________________________________________m
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
