date:20200506

Re: [Pulp-list] Create distribution issues

2020-05-06 Thread Heide, Todd

Reading backwards in the link that was posted in the reply, Under User setup, 
does Pulpcore and pulp-file need to be installed on the same box that pulp 
installer was run on? Maybe that is what I am missing. 

From: Dennis Kliban  
Sent: Wednesday, May 6, 2020 12:00 PM
To: Heide, Todd 
Cc: Pulp-list@redhat.com
Subject: Re: [Pulp-list] Create distribution issues

[EXTERNAL] This message originated outside of the organization. Use caution 
when opening files or following links in this email!
On Tue, May 5, 2020 at 10:40 AM Heide, Todd  
wrote:
New install of 3.3.0 and I can create the repo, 

# http POST http://localhost:24817/pulp/api/v3/repositories/file/file/ name=foo
HTTP/1.1 201 Created
Allow: GET, POST, HEAD, OPTIONS
Connection: close
Content-Length: 376
Content-Type: application/json
Date: Tue, 05 May 2020 14:04:24 GMT
Location: 
/pulp/api/v3/repositories/file/file/7885baed-b707-4002-b1e1-a98924e39ee5/
Server: gunicorn/20.0.4
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN

{
    "description": null,
    "latest_version_href": 
"/pulp/api/v3/repositories/file/file/7885baed-b707-4002-b1e1-a98924e39ee5/versions/0/",
    "name": "foo",
    "pulp_created": "2020-05-05T14:04:24.441705Z",
    "pulp_href": 
"/pulp/api/v3/repositories/file/file/7885baed-b707-4002-b1e1-a98924e39ee5/",
    "versions_href": 
"/pulp/api/v3/repositories/file/file/7885baed-b707-4002-b1e1-a98924e39ee5/versions/"
}

Export the repo
# export REPO_HREF=$(http :24817/pulp/api/v3/repositories/file/file/ | jq -r 
'.results[] | select(.name == "foo") | .pulp_href')

But when I try to make the distribution it errors 404

# http POST :24817/pulp/api/v3/distributions/file/file/ name='baz' 
base_path='mypath' repository=$REPO_HREF``
HTTP/1.1 400 Bad Request
Allow: GET, POST, HEAD, OPTIONS
Connection: close
Content-Length: 35
Content-Type: application/json
Date: Tue, 05 May 2020 14:05:41 GMT
Server: gunicorn/20.0.4
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN

{
    "repository": [
        "Unexpected field"
    ]
}

FileDsitribution requires a publication not a repository. Instructions for that 
are here: 
https://pulp-file.readthedocs.io/en/latest/workflows/publish-host.html#publish-and-host

Did something get missed during the install?   I also tried manual 
distribution, fails at AnsibleRemote
http POST :24817/pulp/api/v3/remotes/ansible/ansible/ name=bar 
url='https://galaxy.ansible.com/api/v1/roles/?/?
> namespace__name=elastic'
HTTP/1.1 404 Not Found
Connection: close
Content-Length: 77
Content-Type: text/html
Date: Tue, 05 May 2020 14:23:20 GMT
Server: gunicorn/20.0.4
X-Frame-Options: SAMEORIGIN

Not FoundThe requested resource was not found on this server.

# http POST :24817/pulp/api/v3/distributions/file/file/ name='baz' 
base_path='dev' repository_version=REPO_VERSION_HREF
HTTP/1.1 400 Bad Request
Allow: GET, POST, HEAD, OPTIONS
Connection: close
Content-Length: 43
Content-Type: application/json
Date: Tue, 05 May 2020 14:24:42 GMT
Server: gunicorn/20.0.4
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN

{
    "repository_version": [
        "Unexpected field"
    ]
}

The only one that seemed to have done anything is manual distribution. 

# http POST :24817/pulp/api/v3/distributions/file/file/ name='baz' 
base_path='bar' publication=$PUBLICATION_HREF
HTTP/1.1 202 Accepted
Allow: GET, POST, HEAD, OPTIONS
Connection: close
Content-Length: 67
Content-Type: application/json
Date: Tue, 05 May 2020 14:35:20 GMT
Server: gunicorn/20.0.4
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN

{
    "task": "/pulp/api/v3/tasks/4c752d6b-9102-4105-b84c-7b523439914a/"
}

So out of the three on this page, 
https://docs.pulpproject.org/workflows/exposing-content.html the only one to 
work is manual distribution of a publication. I can view and download from the 
web page.   Did I miss a plugin or a configuration somewhere? 

A File repository version contains all the files. However, File publications 
always include a manifest file that lists all the files and checksums for those 
files. The manifest is generated only when a publication is created from a 
repository version. 

RPM repositories work the same way and always require generating a publication 
first also. 

___
Pulp-list mailing list
mailto:Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Create distribution issues

2020-05-06 Thread Heide, Todd

Hi, thanks for the reply. I think my issue runs deeper. I found that the GUI is 
missing all the css. When I try to run the scripts that are on those pages that 
are linked, it errors, and then kicks me out.  This is an issue that happened 
from the very beginning, so tried the httpie commands instead listed in my 
first email.  I do see the created repos under /pulp/content/ and under each is 
PULP_MANIFEST. 

Here is what happens, running as root,

# source base.sh
Setting environment variables for default hostname/port for the API and the 
Content app
[root@s_scripts]# source publication.sh
Create a task to create a publication.
parse error: Invalid numeric literal at line 1, column 8
Polling the task until it has reached a final state.
parse error: Invalid numeric literal at line 1, column 8
parse error: Invalid numeric literal at line 1, column 8

I originally tried the repo.sh script to create the first repo, and it failed. 
I modded it to randomly create a name, still failed, though it did create a 
random name.  No matter which one I tried, it comes up the same error.

source base.sh
Setting environment variables for default hostname/port for the API and the 
Content app
[root@aecdas-pulp3test _scripts]# source centos7_os_x64.sh
Creating a new repository named gialy.
parse error: Invalid numeric literal at line 1, column 8
Inspecting Repository.
HTTP/1.1 404 Not Found
Connection: close
Content-Length: 77
Content-Type: text/html
Date: Wed, 06 May 2020 18:49:01 GMT
Server: gunicorn/20.0.4
X-Frame-Options: SAMEORIGIN

Not FoundThe requested resource was not found on this server.

I started on this page  
https://pulp-file.readthedocs.io/en/latest/workflows/scripting.html

So I created a new file called correctness_check.sh and pasted everything in 
from the second script off that page, and same results. 

  source correctness_check.sh
Setting environment variables for default hostname/port for the API and the 
Content app
Creating a new repository named foo.
parse error: Invalid numeric literal at line 1, column 8
Inspecting Repository.
HTTP/1.1 404 Not Found
Connection: close
Content-Length: 77
Content-Type: text/html
Date: Wed, 06 May 2020 18:55:30 GMT
Server: gunicorn/20.0.4
X-Frame-Options: SAMEORIGIN

Not FoundThe requested resource was not found on this server.

Creating a remote that points to an external source of files.
HTTP/1.1 404 Not Found
Connection: close
Content-Length: 77
Content-Type: text/html
Date: Wed, 06 May 2020 18:55:31 GMT
Server: gunicorn/20.0.4
X-Frame-Options: SAMEORIGIN

Not FoundThe requested resource was not found on this server.

Export an environment variable for the new remote URI.
parse error: Invalid numeric literal at line 1, column 8
Inspecting new Remote.
HTTP/1.1 404 Not Found
Connection: close
Content-Length: 77
Content-Type: text/html
Date: Wed, 06 May 2020 18:55:31 GMT
Server: gunicorn/20.0.4
X-Frame-Options: SAMEORIGIN

Not FoundThe requested resource was not found on this server.

Create a task to sync the repository using the remote.

http: error: InvalidURL: Failed to parse: localhost:24817sync
Polling the task until it has reached a final state.
parse error: Invalid numeric literal at line 1, column 8
parse error: Invalid numeric literal at line 1, column 8

It all goes back to that first parsing error. So I am not sure what is going 
on, but following the Ansible Install should have a working system, but with 
missing CSS for the GUI, and these parsing errors, I am not sure what is going 
on. 


Here is one of the repo scripts I created and ran that built and published the 
repos based on examples from the link in my previous email.

#!/bin/bash

# Create a Repository

http POST :24817/pulp/api/v3/repositories/file/file/ name=Centos7-os-x86_64

export REPO_HREF=$(http :24817/pulp/api/v3/repositories/file/file/ | jq -r 
'.results[] | select(.name == "Centos7-os-x86_64") | .pulp_href')

# Create an FileRemote to sync roles from Centos
http POST :24817/pulp/api/v3/remotes/file/file/ name='Centos7-os' 
url='http://mirror.centos.org/centos/7/os/x86_64/'
export REMOTE_HREF=$(http :24817/pulp/api/v3/remotes/file/file/ | jq -r 
'.results[] | select(.name == "Centos7-os") | .pulp_href')

# Sync the repo with the remote
http POST ':24817'$REPO_HREF'sync/' remote=$REMOTE_HREF
sleep 3  # wait for the sync to happen

# Create a Publication
http POST :24817/pulp/api/v3/publications/file/file/ repository=$REPO_HREF
export PUBLICATION_HREF=$(http :24817/pulp/api/v3/publications/file/file/ | jq 
-r '.results[0] | .pulp_href')

#Publish
http POST :24817/pulp/api/v3/distributions/file/file/ name='base' 
base_path='Centos7' publication=$PUBLICATION_HREF



From: Dennis Kliban  
Sent: Wednesday, May 6, 2020 12:00 PM
To: Heide, Todd 
Cc: Pulp-list@redhat.com
Subject: Re: [Pulp-list] Create distribution issues

[EXTERNAL] This message originated outside of the organization. Use caution 
when opening files or following links in this email!
On Tue, May 5, 2020 at 10:40 AM

Re: [Pulp-list] pulpcore-client 3.2 ldap authentication

2020-05-06 Thread Bin Li (BLOOMBERG/ 120 PARK)

I wonder if we could set the below in /etc/pulp/settings.py. The doc use a 
tuple. I replaced with a list since I couldn't figure out how to set a tuple in 
ansible pulp_installer. It seems to work.

REST_FRAMEWORK__DEFAULT_AUTHENTICATION_CLASSES = 
["rest_framework.authentication.SessionAuthentication", "pulpcore.app.authentica
tion.PulpRemoteUserAuthentication"]


Thanks.
From: Bin Li (BLOOMBERG/ 120 PARK) At: 04/24/20 22:40:15To:  dkli...@redhat.com
Cc:  pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
Thanks Dennis. It works now by setting proxy_set_header REMOTE_USER 'admin' in 
nginx.conf. It was set to $remote_user.

From: dkli...@redhat.com At: 04/23/20 08:11:20To:  Bin Li (BLOOMBERG/ 120 PARK 
) 
Cc:  pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication

All the settings look correct to me. It seems like nginx is not setting 
HTTP_REMOTE_USER header on the request it passes to guincorn. The value of this 
header needs to always be 'admin' since that is the only user in the system 
right now. 

On Wed, Apr 22, 2020 at 9:43 AM Bin Li (BLOOMBERG/ 120 PARK) 
 wrote:

Django app detected
Working in development environment 
BASE_DIR 
'/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app'
DEBUG False
ALLOWED_HOSTS ['*']
MEDIA_ROOT '/var/lib/pulp/'
STATIC_ROOT '/var/lib/pulp/assets/'
DEFAULT_FILE_STORAGE 'pulpcore.app.models.storage.FileSystem'
FILE_UPLOAD_TEMP_DIR '/var/lib/pulp/tmp/'
WORKING_DIRECTORY '/var/lib/pulp/tmp/'
FILE_UPLOAD_HANDLERS ['pulpcore.app.files.HashingFileUploadHandler']
SECRET_KEY '3e$d+861lqv8x6y39p%^0!3(=%jzw6()g!u44%(=u@1_5p42g!'
INSTALLED_APPS ['django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'django_filters',
 'drf_yasg',
 'rest_framework',
 'pulpcore.app',
 'pulp_rpm.app.PulpRpmPluginAppConfig',
 'pulp_file.app.PulpFilePluginAppConfig']
INSTALLED_PULP_PLUGINS ['pulp_rpm', 'pulp_file']
OPTIONAL_APPS ['crispy_forms', 'django_extensions', 'storages']
MIDDLEWARE ['django.middleware.security.SecurityMiddleware',
 'whitenoise.middleware.WhiteNoiseMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware']
AUTHENTICATION_BACKENDS 
['pulpcore.app.authentication.PulpNoCreateRemoteUserBackend']
ROOT_URLCONF 'pulpcore.app.urls'
TEMPLATES [{'APP_DIRS': True,
  'BACKEND': 'django.template.backends.django.DjangoTemplates',
  'DIRS': 
['/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/templates'],
  'OPTIONS': {'context_processors': ['django.template.context_processors.debug',
 
'django.template.context_processors.request',
 
'django.contrib.auth.context_processors.auth',
 
'django.contrib.messages.context_processors.messages']}}]
WSGI_APPLICATION 'pulpcore.app.wsgi.application'
REST_FRAMEWORK {'DEFAULT_AUTHENTICATION_CLASSES': 
['rest_framework.authentication.SessionAuthentication',

'pulpcore.app.authentication.PulpRemoteUserAuthentication'],
 'DEFAULT_FILTER_BACKENDS': 
['django_filters.rest_framework.DjangoFilterBackend'],
 'DEFAULT_PAGINATION_CLASS': 'rest_framework.pagination.LimitOffsetPagination',
 'DEFAULT_PERMISSION_CLASSES': ['rest_framework.permissions.IsAuthenticated'],
 'DEFAULT_VERSIONING_CLASS': 'rest_framework.versioning.URLPathVersioning',
 'PAGE_SIZE': 100,
 'UPLOADED_FILES_USE_URL': False,
 'URL_FIELD_NAME': 'pulp_href'}
AUTH_PASSWORD_VALIDATORS [{'NAME': 
'django.contrib.auth.password_validation.UserAttributeSimilarityValidator'},
 {'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator'},
 {'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator'},
 {'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator'}]
LANGUAGE_CODE 'en-us'
TIME_ZONE 'UTC'
USE_I18N ['USE_I18N', True]
USE_L10N True
USE_TZ True
STATIC_URL '/static/'
DATABASES {'default': {'ENGINE': 'django.db.backends.postgresql_psycopg2',
 'HOST': 'localhost',
 'NAME': 'pulp',
 'PASSWORD': 'pulp',
 'PORT': 5432,
 'USER': 'pulp'}}
LOGGING {'disable_existing_loggers': False,
 'formatters': {'simple': {'format': 'pulp: %(name)s:%(levelname)s: '
 '%(message)s'}},
 'handlers': {'console': {'class': 'logging.StreamHandler',
  'formatter': 'simple'}},
 'loggers': {'': {'handlers': ['console'], 'level': 'INFO'}},
 'version': 1}
CONTENT_PATH_PREFIX '/pulp/content/'
CONTENT_APP_TTL 120
REMOTE_USER_ENVIRON_NAME

Re: [Pulp-list] [Pulp-dev] Pulp 3 CLI MVP

2020-05-06 Thread Dennis Kliban

On Wed, May 6, 2020 at 12:30 PM David Davis  wrote:

> Matthias and I met today to go over some plans for a prototype. I wrote
> some notes[0] down. As part of the prototype, we'd propose two deliverables
> (one this week and one next week):
>
> 1. A set of ~2-3 click commands that use the bindings to interact with Pulp
> 2. Some openapi-generator templates that will be able to generate such
> commands from the schema
>
> There is a question we had about how the commands for typed resources will
> be structured in the CLI. To illustrate with two endpoints:
>
>
We should call the command 'pulp' instead of pulp-cli.


> # rpm.package content (/pulp/api/v3/content/rpm/packages/):
> - pulp-cli rpm content packages ...
> - pulp-cli content rpm packages ...
> - pulp-cli rpm packages content ...
> - ???
>

I was thinking we should structure the commands similar to the URLs in the
REST API.

pulp content rpm packages


>
> # file.file repositories (/pulp/api/v3/repositories/file/file/):
> - pulp-cli file repositories file ...
> - pulp-cli repositories file file ...
> - pulp-cli file file repositories ...
> - ???
>
> pulp repositories file

Plugins that provide multiple types of the same resource would need to be
more descriptive. Though I can see a practical reason for requiring all
resources to be that descriptive.

pulp repositories rpm rpm
pulp repositories rpm mirror



> [0] https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig?view#Prototype
>
> David
>
>
> On Thu, Apr 30, 2020 at 1:42 PM David Davis  wrote:
>
>> Today we met to discuss some ideas for a technical design for how the CLI
>> would work. Here's a copy of our notes:
>>
>> https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig#Technical-discussion
>>
>> And there is a rough design in the document as well:
>>
>> https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig#Design
>>
>> I have also entered the CLI user stories from our meeting last week into
>> redmine under the Pulp CLI project:
>>
>> https://pulp.plan.io/versions/93
>>
>> And I've filed a user story that we talked about today that would handle
>> sync, publish, and distribution of repos. Feedback welcome:
>>
>> https://pulp.plan.io/issues/6626
>>
>> Matthias and I are planning to meet next week to look at creating a proof
>> of concept that would provide 2-3 commands. If anyone is interested in
>> joining us, please let me know and I can add you.
>>
>> David
>>
>>
>> On Tue, Apr 28, 2020 at 8:06 AM David Davis 
>> wrote:
>>
>>> I've also started working on some questions about how the CLI will work.
>>> Feel free to add some of your own:
>>>
>>> https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig?view#Technical-discussion
>>>
>>> David
>>>
>>>
>>> On Tue, Apr 28, 2020 at 8:05 AM David Davis 
>>> wrote:
>>>
 I have set up a meeting to discuss the CLI technical design. Below are
 the details. I think a video conference might be easier for technical
 discussion but am open to consider meeting on #pulp-meeting again.

 URL: https://meet.google.com/vgx-bzbb-wnh
 Date/time: April 30, 2020 at 9:00am ET (1pm UTC)

 David


 On Fri, Apr 24, 2020 at 10:29 AM David Davis 
 wrote:

> Today we met in #pulp-meeting on freenode to discuss the user stories
> for a Pulp 3 CLI MVP. The document with the user stories is available
> below. I'd like to ask for any feedback from users or plugin writers.
>
> The goal of the CLI MVP is to cover the pulp_file happy path (sync,
> publish, distribute) and make it possible for plugin writers to generate
> and write their own commands. I'm imagining that plugins will release 
> their
> own sets of CLI commands after we complete the initial MVP.
>
> https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig
>
> Feedback is welcome. I plan to enter these user stories into redmine
> next week.
>
> David
>
 ___
> Pulp-dev mailing list
> pulp-...@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Create distribution issues

2020-05-06 Thread Dennis Kliban

On Tue, May 5, 2020 at 10:40 AM Heide, Todd 
wrote:

> New install of 3.3.0 and I can create the repo,
>
> # http POST http://localhost:24817/pulp/api/v3/repositories/file/file/
> name=foo
> HTTP/1.1 201 Created
> Allow: GET, POST, HEAD, OPTIONS
> Connection: close
> Content-Length: 376
> Content-Type: application/json
> Date: Tue, 05 May 2020 14:04:24 GMT
> Location:
> /pulp/api/v3/repositories/file/file/7885baed-b707-4002-b1e1-a98924e39ee5/
> Server: gunicorn/20.0.4
> Vary: Accept, Cookie
> X-Frame-Options: SAMEORIGIN
>
> {
> "description": null,
> "latest_version_href":
> "/pulp/api/v3/repositories/file/file/7885baed-b707-4002-b1e1-a98924e39ee5/versions/0/",
> "name": "foo",
> "pulp_created": "2020-05-05T14:04:24.441705Z",
> "pulp_href":
> "/pulp/api/v3/repositories/file/file/7885baed-b707-4002-b1e1-a98924e39ee5/",
> "versions_href":
> "/pulp/api/v3/repositories/file/file/7885baed-b707-4002-b1e1-a98924e39ee5/versions/"
> }
>
> Export the repo
> # export REPO_HREF=$(http :24817/pulp/api/v3/repositories/file/file/ | jq
> -r '.results[] | select(.name == "foo") | .pulp_href')
>
> But when I try to make the distribution it errors 404
>
> # http POST :24817/pulp/api/v3/distributions/file/file/ name='baz'
> base_path='mypath' repository=$REPO_HREF``
> HTTP/1.1 400 Bad Request
> Allow: GET, POST, HEAD, OPTIONS
> Connection: close
> Content-Length: 35
> Content-Type: application/json
> Date: Tue, 05 May 2020 14:05:41 GMT
> Server: gunicorn/20.0.4
> Vary: Accept, Cookie
> X-Frame-Options: SAMEORIGIN
>
> {
> "repository": [
> "Unexpected field"
> ]
> }
>
>
FileDsitribution requires a publication not a repository. Instructions for
that are here:
https://pulp-file.readthedocs.io/en/latest/workflows/publish-host.html#publish-and-host


> Did something get missed during the install?   I also tried manual
> distribution, fails at AnsibleRemote
> http POST :24817/pulp/api/v3/remotes/ansible/ansible/ name=bar url='
> https://galaxy.ansible.com/api/v1/roles/?
> > namespace__name=elastic'
> HTTP/1.1 404 Not Found
> Connection: close
> Content-Length: 77
> Content-Type: text/html
> Date: Tue, 05 May 2020 14:23:20 GMT
> Server: gunicorn/20.0.4
> X-Frame-Options: SAMEORIGIN
>
> Not FoundThe requested resource was not found on this
> server.
>
> # http POST :24817/pulp/api/v3/distributions/file/file/ name='baz'
> base_path='dev' repository_version=REPO_VERSION_HREF
> HTTP/1.1 400 Bad Request
> Allow: GET, POST, HEAD, OPTIONS
> Connection: close
> Content-Length: 43
> Content-Type: application/json
> Date: Tue, 05 May 2020 14:24:42 GMT
> Server: gunicorn/20.0.4
> Vary: Accept, Cookie
> X-Frame-Options: SAMEORIGIN
>
> {
> "repository_version": [
> "Unexpected field"
> ]
> }
>
> The only one that seemed to have done anything is manual distribution.
>
> # http POST :24817/pulp/api/v3/distributions/file/file/ name='baz'
> base_path='bar' publication=$PUBLICATION_HREF
> HTTP/1.1 202 Accepted
> Allow: GET, POST, HEAD, OPTIONS
> Connection: close
> Content-Length: 67
> Content-Type: application/json
> Date: Tue, 05 May 2020 14:35:20 GMT
> Server: gunicorn/20.0.4
> Vary: Accept, Cookie
> X-Frame-Options: SAMEORIGIN
>
> {
> "task": "/pulp/api/v3/tasks/4c752d6b-9102-4105-b84c-7b523439914a/"
> }
>
>
> So out of the three on this page,
> https://docs.pulpproject.org/workflows/exposing-content.html the only one
> to work is manual distribution of a publication. I can view and download
> from the web page.   Did I miss a plugin or a configuration somewhere?
>
>
A File repository version contains all the files. However, File
publications always include a manifest file that lists all the files and
checksums for those files. The manifest is generated only when a
publication is created from a repository version.

RPM repositories work the same way and always require generating a
publication first also.



>
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 3 CLI MVP

2020-05-06 Thread David Davis

Matthias and I met today to go over some plans for a prototype. I wrote
some notes[0] down. As part of the prototype, we'd propose two deliverables
(one this week and one next week):

1. A set of ~2-3 click commands that use the bindings to interact with Pulp
2. Some openapi-generator templates that will be able to generate such
commands from the schema

There is a question we had about how the commands for typed resources will
be structured in the CLI. To illustrate with two endpoints:

# rpm.package content (/pulp/api/v3/content/rpm/packages/):
- pulp-cli rpm content packages ...
- pulp-cli content rpm packages ...
- pulp-cli rpm packages content ...
- ???

# file.file repositories (/pulp/api/v3/repositories/file/file/):
- pulp-cli file repositories file ...
- pulp-cli repositories file file ...
- pulp-cli file file repositories ...
- ???

[0] https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig?view#Prototype

David


On Thu, Apr 30, 2020 at 1:42 PM David Davis  wrote:

> Today we met to discuss some ideas for a technical design for how the CLI
> would work. Here's a copy of our notes:
>
> https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig#Technical-discussion
>
> And there is a rough design in the document as well:
>
> https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig#Design
>
> I have also entered the CLI user stories from our meeting last week into
> redmine under the Pulp CLI project:
>
> https://pulp.plan.io/versions/93
>
> And I've filed a user story that we talked about today that would handle
> sync, publish, and distribution of repos. Feedback welcome:
>
> https://pulp.plan.io/issues/6626
>
> Matthias and I are planning to meet next week to look at creating a proof
> of concept that would provide 2-3 commands. If anyone is interested in
> joining us, please let me know and I can add you.
>
> David
>
>
> On Tue, Apr 28, 2020 at 8:06 AM David Davis  wrote:
>
>> I've also started working on some questions about how the CLI will work.
>> Feel free to add some of your own:
>>
>> https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig?view#Technical-discussion
>>
>> David
>>
>>
>> On Tue, Apr 28, 2020 at 8:05 AM David Davis 
>> wrote:
>>
>>> I have set up a meeting to discuss the CLI technical design. Below are
>>> the details. I think a video conference might be easier for technical
>>> discussion but am open to consider meeting on #pulp-meeting again.
>>>
>>> URL: https://meet.google.com/vgx-bzbb-wnh
>>> Date/time: April 30, 2020 at 9:00am ET (1pm UTC)
>>>
>>> David
>>>
>>>
>>> On Fri, Apr 24, 2020 at 10:29 AM David Davis 
>>> wrote:
>>>
 Today we met in #pulp-meeting on freenode to discuss the user stories
 for a Pulp 3 CLI MVP. The document with the user stories is available
 below. I'd like to ask for any feedback from users or plugin writers.

 The goal of the CLI MVP is to cover the pulp_file happy path (sync,
 publish, distribute) and make it possible for plugin writers to generate
 and write their own commands. I'm imagining that plugins will release their
 own sets of CLI commands after we complete the initial MVP.

 https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig

 Feedback is welcome. I plan to enter these user stories into redmine
 next week.

 David

>>>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Create distribution issues

Re: [Pulp-list] Create distribution issues

Re: [Pulp-list] pulpcore-client 3.2 ldap authentication

Re: [Pulp-list] [Pulp-dev] Pulp 3 CLI MVP

Re: [Pulp-list] Create distribution issues

Re: [Pulp-list] Pulp 3 CLI MVP

6 matches

Site Navigation

Mail list logo

Footer information