Project

Profile

Help

Story #3927

closed

As a user, I can upload information about Consumer

Added by dkliban@redhat.com almost 6 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
2.18.0
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

As a result of this story the user will be able to upload a set of reports about a consumer. The payload will look like this:

{
  "content_type": "modulemd",
  "profile": [{"name": "duck",
               "stream": 0,
               "version": "20180730233102",
               "context": "deadbeef",
               "arch": "noarch"},
               {"name": "flipper",
               "stream": 0.71,
               "version": "20180707144203",
               "context": "c0ffee42",
               "arch": "x86_64"}
               ]
}
{
  "content_type": “rpm",
  "profile": [ {"name": "duck_the_second",
               "version": 2,
               "release”: "livebeef",
               "arch": "noarch",
               "epoch": "default",
               “vendor”:”RH”},
               ]
}

The "profiles" field on the actual module object reflects the enabled profiles for that module.
Pulp's applicability APIs will then be able to use this profile to calculate applicability to a consumer.

Profile for rpm type seems to be the same as before, so no migration is needed.


Related issues

Related to RPM Support - Test #4158: Test applicability for modular or mixed contentCLOSED - COMPLETEActions
Blocks RPM Support - Story #4058: As a user, I can calculate applicability for modular contentCLOSED - CURRENTRELEASEttereshc

Actions
Actions #1

Updated by dkliban@redhat.com over 5 years ago

  • Sprint/Milestone deleted (2.18.0)
Actions #2

Updated by ttereshc over 5 years ago

  • Blocks Story #4058: As a user, I can calculate applicability for modular content added
Actions #3

Updated by ttereshc over 5 years ago

  • Subject changed from As a user, I can upload a Consumer Profile for 'modulemd' content type. to As a user, I can upload information about Consumer
  • Description updated (diff)
Actions #4

Updated by ttereshc over 5 years ago

  • Description updated (diff)

How/where to store info about enabled modules?

I think that enabled modules semantically are closer to enabled repositories.
We have a consumer_bindings collection. We can create a new collection for mapping of a consumer and modules.

Alternatively, profile for modulemd type can be stored on the consumer_profiles collection, just under different type, not rpm.
But then repo_profile_applicability would need to refer to both of these profiles (or to hash from two profile hashes).

I think the former option is more clear and straightforward.
Any preference or other suggestions?

Actions #5

Updated by ttereshc over 5 years ago

  • Sprint/Milestone set to 2.18.0
Actions #6

Updated by jortel@redhat.com over 5 years ago

ttereshc wrote:

Alternatively, profile for modulemd type can be stored on the consumer_profiles collection, just under different type, not rpm.
But then repo_profile_applicability would need to refer to both of these profiles (or to hash from two profile hashes).

This ^ is why the profiles collection supports type. It is intended to store more than just installed rpms and I think would be the appropriate place to inventory enabled modules.

Actions #7

Updated by ttereshc over 5 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc
Actions #8

Updated by ttereshc over 5 years ago

  • Description updated (diff)
Actions #9

Updated by ttereshc over 5 years ago

  • Description updated (diff)
Actions #10

Updated by ttereshc over 5 years ago

  • Related to Test #4158: Test applicability for modular or mixed content added

Added by ttereshc over 5 years ago

Revision 3a9a314b | View on GitHub

Applicability calculation supports modularity content

  • support upload of modulemd profiles
  • applicability is calculated with module info taken into consideration
  • report contains applicable RPMs, Modulemds and Errata

closes #4058 https://pulp.plan.io/issues/4058

closes #3925 https://pulp.plan.io/issues/3925

closes #3927 https://pulp.plan.io/issues/3927

Actions #11

Updated by ttereshc over 5 years ago

  • Status changed from ASSIGNED to MODIFIED
  • % Done changed from 0 to 100
Actions #12

Updated by ttereshc over 5 years ago

  • Platform Release set to 2.18.0
Actions #13

Updated by ttereshc over 5 years ago

  • Status changed from MODIFIED to 5
Actions #14

Updated by ttereshc over 5 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions #15

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF