** Description changed: - - For Clouds that have support in later or development version of Cloud-init, Canonical allows for Cloud Vendors to backport the datasource and dependencies to under the following rules: - - Only Datasources which have been submitted to upstream or are in upstream cloud-init are eligible for backporting. - Only the Datasource and dependencies of the datasource should be backported - Dependencies upon cloud-init internals from a future release should be either added to the backported Datasource or added to a new class. - Features and cloud-config modules are NOT to be backported. - Backporting complete versions of Cloud-init to prior releases is expressly prohibited. - The backported Datasource should be packaged and named “cloud-init-ds-<cloud>” - The package MUST conflict with the version of cloud-init where the Datasource is provided natively by Cloud-init - A package must exist for each supported version of Ubuntu between the target version of Ubuntu and where native support appears. - For example, if backporting a Datasource in 14.04 to 12.04, a backport for any version between 12.04 and 14.04 that is currently supported must exist. - End-of-life’d versions of Ubuntu are excluded from this requirement as they are no longer supported. For exmaple, 13.10 reaches EOL in July 2014. This means that Clouds that backport Datasources to 12.04 would only need to maintain 13.10 till July 2014, after which the Cloud would only need to maintain 12.04. - Clouds must test upgradability to make sure that a user upgrading versions is not broken. - Packages must conform to the Debian packaging standards - The Cloud needs to establish a support channel for the Datasource - The Cloud assumes all support and bug issues - Canonical will accept bugs related to the Datasource and Cloud-init interaction if and only if the Cloud can show that the issue is with Cloud-init and not with the Datasource. - The package may configure cloud-init to use the Datasource. - The package MUST NOT change the installed package for cloud-init (i.e. Clouds should not change packaged files included in the cloud-init package). - The package should write a manifest file to /etc/cloud/datasource-<cloud>.cfg - The manifest should include a changelog - The manifest should identify the version of Cloud-init where the datasource came from. - - Canonical does not provide guidance or documentation for Clouds - performing backport work. The work involved requires an expert in Python - and Debian packaging. - - However, Canonical does offer the backporting of Cloud-init Datasources - on a per-fee basis. When performed by Canonical, the backports are added - to the Cloud-init package as part of the Ubuntu SRU process and will be - maintained by Canonical. - - - for more information see: - https://docs.google.com/a/canonical.com/document/d/17KIBUhcIHjYInglxlVnYluNNX6xzaFog2WaEUP5DFyk/edit# + Invalid bug
** Information type changed from Public to Private ** Summary changed: - Cloud-init Datasource backporting via PPA + Bug is invalid and private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304075 Title: Bug is invalid and private To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1304075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
