Re: Oracle Cloud Infrastructure introduction
On Tue, Oct 27, 2020 at 12:00:54PM -0700, Paul Graydon wrote:
> Okay, that sounds like a reasonable route forwards here. Are there any
> restrictions around what we can/cannot do, while retaining the Debian
> branding, as it were? For example, with the CentOS images (that we build
> and publish), there are some tight restrictions around what we install in
> the images. The main obvious thing there that I'd imagine applies with
> Debian too, is no installation of packages of a different version for that
> that is packaged and shipped by them in their repository (so no replacing
> the kernel, systemd, etc. etc.), at least not while still referring to it as
> "CentOS".
We've mentioned the first restriction: only components from Debian main
can be included. It's not just that you can't replace packaged
software, it's that all software must be packaged.
The second is that official images must be built on Debian-owned
hardware by the cloud team. As long as the tools get extended with OCI
support, our pipeline takes care of this.
Third (I think last?) - images must be distributed from an account that
Software in the Public Interest (spi-inc.org) owns and operates on
behalf of Debian. Debian's legal existence is unclear, so we need a
trusted entity to negotiate and accept agreements for operating on OCI.
This can be a challenging process - I wouldn't wait on it to start
technical work, if you decide to pursue an official image.
Ross
Reply to: