Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-06-04T13:49:06ZPulp
Planio Pulp - Story #1029 (CLOSED - WONTFIX): Automatically verify release note existence in the test ru...https://pulp.plan.io/issues/10292015-06-04T13:49:06Zbcourtbcourt@redhat.com
<p>In pulp/devel/test_runner.py optionally verify the standard release notes exist for the version specified in a project spec file.</p>
<p>Each project would provide an optional release_notes_dir argument when they call pulp/devel/test_runner.py. If this is specified then<br>
1) Get the current version being built from the spec file in the project root<br>
2) Validate that a <release_notes_dir>/<major>.<minor>.x.rst file exists<br>
3) Validate that the major.minor.version number exists in the rst file</p> RPM Support - Issue #951 (CLOSED - CURRENTRELEASE): checksum is not honored if sqlite generation ...https://pulp.plan.io/issues/9512015-05-05T18:51:45Zbcourtbcourt@redhat.com
<p>If sqlite generation is enabled the checksum is always using sha256</p> Debian Support - Refactor #878 (CLOSED - CURRENTRELEASE): Convert pulp_deb to use MongoEngine modelshttps://pulp.plan.io/issues/8782015-04-10T17:35:20Zbcourtbcourt@redhat.com
<p>Convert the pulp_deb to use MongoEngine models for all unit actions instead of the associated unit</p>
<p>Deliverables:</p>
<ul>
<li>ContentUnit model for docker_image units
<ul>
<li>The model is registered via the entry point</li>
<li>The types .json file is removed, and references to it in the spec files are are also removed</li>
</ul>
</li>
<li>All interactions with units in the plugin use the new unit model and the Repository model for creating, saving and updating units</li>
<li>Convert the model according to the <a href="https://fedorahosted.org/pulp/wiki/ConvertingModelsToMongoengine#StepsinvolvedinconvertingaPulpmodeltoMongoEngine" class="external">conversion guide</a>
</li>
</ul>
<p>Supported operations:</p>
<p>Milestone 1:</p>
<ul>
<li>Create repository to host deb packages</li>
<li>Add deb unit to deb repository (implementation detail: importer needs to work)</li>
<li>Publish apt repository (implementation detail: distributor needs to work)</li>
<li>Sign repository metadata within the distributor</li>
</ul>
<p>Milestone 2:</p>
<ul>
<li>Ability to sync a repo produced at milestone 1 (one dist, one component, one architecture)</li>
</ul>
<p>To be done later:</p>
<ul>
<li>Full mirror support - problematic for several reasons:
<ul>
<li>we need a way to keep track of which deb unit came from which dist/component/architecture</li>
<li>in order to not invalidate the repo metadata signature, we may have to save the repo metadata files and publish exactly those.</li>
</ul>
</li>
<li>Partial mirror
<ul>
<li>ability to specify a whitelist of dist/component/architecture combinations to be synced</li>
</ul>
</li>
</ul> OSTree Support - Refactor #876 (CLOSED - CURRENTRELEASE): Convert pulp_ostree to use MongoEngine ...https://pulp.plan.io/issues/8762015-04-10T17:32:26Zbcourtbcourt@redhat.com
<p>Convert the pulp_ostree to use MongoEngine models for all unit actions instead of the associated unit</p>
<p>Deliverables:</p>
<ul>
<li>ContentUnit model for docker_image units
<ul>
<li>The model is registered via the entry point</li>
<li>The types .json file is removed, and references to it in the spec files are are also removed</li>
</ul>
</li>
<li>All interactions with units in the plugin use the new unit model and the Repository model for creating, saving and updating units</li>
</ul> Puppet Support - Refactor #875 (CLOSED - CURRENTRELEASE): Convert pulp_puppet to use MongoEngine ...https://pulp.plan.io/issues/8752015-04-10T17:31:24Zbcourtbcourt@redhat.com
<p>Convert the pulp_puppet to use MongoEngine models for all unit actions instead of the associated unit</p>
<p>Deliverables:</p>
<ul>
<li>ContentUnit model for docker_image units
<ul>
<li>The model is registered via the entry point</li>
<li>The types .json file is removed, and references to it in the spec files are are also removed</li>
</ul>
</li>
<li>All interactions with units in the plugin use the new unit model and the Repository model for creating, saving and updating units</li>
</ul> Pulp - Refactor #873 (CLOSED - WONTFIX): Add support for loading types via MongoEngine models to ...https://pulp.plan.io/issues/8732015-04-10T16:13:12Zbcourtbcourt@redhat.com
<p>Add support for loading types via MongoEngine models to the server initialization (in addition to the content_types collection).</p>
<p>After this, types can be loaded via either the entry point or the types.json</p> Docker Support - Refactor #863 (CLOSED - CURRENTRELEASE): Convert pulp_docker to use MongoEngine ...https://pulp.plan.io/issues/8632015-04-10T15:32:38Zbcourtbcourt@redhat.com
<p>Convert the pulp_docker to use MongoEngine models for all unit actions instead of the associated unit</p>
<p>Deliverables:</p>
<ul>
<li>ContentUnit model for docker_image units
<ul>
<li>The model is registered via the entry point</li>
<li>The types .json file is removed, and references to it in the spec files are are also removed</li>
</ul>
</li>
<li>All interactions with units in the plugin use the new unit model and the Repository model for creating, saving and updating units</li>
</ul> Pulp - Refactor #862 (CLOSED - CURRENTRELEASE): Add unit association and querying support to the ...https://pulp.plan.io/issues/8622015-04-10T14:59:46Zbcourtbcourt@redhat.com
<p>Add the ability to query units via the Repository model</p>
<ul>
<li>Add method find_units(association_q, unit_q, limit, skip) that returns an iterable. This iterable yields repo_content_units with a 'unit' attribute on each item that is filled in by the find_units iterator(), if limit is unspecified all units will be returned, if skip is unspecified then the first batch will be returned</li>
<li>Add method add_unit(model) that creates/updates the repo_content_unit collection entry for the unit</li>
<li>Add method add_units(model_iterable) that creates/updates the repo_content_unit collection entry for every model in the iterable.</li>
<li>content_unit_counts should be updated automatically whenever units are added or removed from the repository</li>
<li>Add a method to remove_unit(unit_model) remove a unit by passing in the unit object.</li>
<li>Add a method to remove_units(association_qs, unit_qs) to remove units matching a filter.</li>
</ul> Crane - Story #260 (CLOSED - WONTFIX): [RFE] Crane should install a default /etc/crane.confhttps://pulp.plan.io/issues/2602015-02-19T01:19:48Zbcourtbcourt@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1150222" class="external">Bugzilla Bug #1150222</a> +</span>+</p>
<p>Description of problem:</p>
<p>Crane should create a default /etc/crane.conf that is commented out similarly to the /etc/pulp/server.conf.</p> Pulp - Story #259 (CLOSED - WONTFIX): [RFE] Automatically load global configuration for pluginshttps://pulp.plan.io/issues/2592015-02-19T01:19:44Zbcourtbcourt@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1150162" class="external">Bugzilla Bug #1150162</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:</p>
<p>Currently all plugins have to specify their global configuration file and load it manually. The platform should automatically look for a server/plugin.conf.d/<plugin_id>.ini file and use that for the global plugin configuration.</p> Pulp - Story #258 (CLOSED - WONTFIX): [RFE] Use the same configuration file format everywhere in ...https://pulp.plan.io/issues/2582015-02-19T01:19:41Zbcourtbcourt@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1150153" class="external">Bugzilla Bug #1150153</a> +</span>+</p>
<p>Description of problem:</p>
<p>Currently we have configuration files in both INI and JSON format. The server plugin.conf.d format is json and the rest of the pulp configuration files are in ini format. This is confusing to the user. We should use the same format for<br>
configuration files everywhere. I would propose that we use ini files everywhere since as a format it allows us to include comments that show all the valid keys that could be filled in.</p>
<p>--- Additional comment from <a href="mailto:mhrivnak@redhat.com" class="email">mhrivnak@redhat.com</a> at 10/10/2014 16:20:50 ---</p>
<p>This will definitely impact katello, so keep them in the loop.</p> Packaging - Task #151 (CLOSED - CURRENTRELEASE): Add automation to perform beta/release builds.https://pulp.plan.io/issues/1512015-02-06T19:17:26Zbcourtbcourt@redhat.com
<p>Assumptions:</p>
<ul>
<li>All projects built using this framework use the x.y-dev,x.y-testing,x.y-release</li>
<li>RPM signing is still completed manually</li>
<li>The spec files in the x.y-testing repository will have their versions bumped when the content is merged from x.y-dev or when the first new commit is added after a release build. This is not auto-bumped as part of the release build as we would have no way to know if no changes have been added to a project.</li>
</ul> Packaging - Task #89 (CLOSED - CURRENTRELEASE): Add automation to run unit tests for all PRs agai...https://pulp.plan.io/issues/892015-01-05T21:24:17Zbcourtbcourt@redhat.com
<p>Us the jenkins github pull request builder plugin to build all PRs against the core Pulp project automatically. This includes creating comments on the PRs indicating the success/failure of the test run.</p>
<p>This will require dynamically figuring out which nightly repo should be used to install the base pulp and plugin.</p>
<p>General procedure for running the unit tests</p>
<ol>
<li>Determine the base repository to install from</li>
<li>Install @pulp-server-qpid</li>
<li>Install the plugin that is being tested from RPM (this will ensure all dependencies are installed)</li>
<li>Uninstall the plugin that is being tested</li>
<li>Install the plugin from source</li>
<li>Run the tests</li>
</ol> Pulp - Task #85 (CLOSED - CURRENTRELEASE): Add automation to run unit tests for all PRs against p...https://pulp.plan.io/issues/852015-01-02T18:06:20Zbcourtbcourt@redhat.com
<p>Us the jenkins github pull request builder plugin to build all PRs against the core Pulp project automatically. This includes creating comments on the PRs indicating the success/failure of the test run.</p> Puppet Support - Story #83 (CLOSED - CURRENTRELEASE): As a user I can install puppet modules usin...https://pulp.plan.io/issues/832014-12-19T21:40:05Zbcourtbcourt@redhat.com
<p>As a user I can install a module using the puppet module install command line using the v3 forge api enumerated at <a href="https://forgeapi.puppetlabs.com/" class="external">https://forgeapi.puppetlabs.com/</a></p>
<p>This will entail creating a new /v3/releases endpoint. We will have to go back to the pre-puppet 3.3 method of determining the repository and consumer as the ability to specify a context root has been disabled.</p>
<p>The api now requires pagination, offset tracking, and providing the urls for the next/previous queries in the case of pagination.<br>
There are now many more options for filtering.</p>
<p>We will only have to support the /v3/releases endpoint at this time.</p>