[Pulp-list] pulp_rpm 3.3.0 GA

2020-04-23 Thread Daniel Alley
pulp_rpm 3.3.0 has been released. It is compatible with pulpcore 3.3.

Among other features, this release includes:
 - ability to perform complicated copy scenarios, including filters and
dependency solving
 - repository metadata signing

For the full list of features, see the changelog.

PyPI: https://pypi.org/project/pulp-rpm/3.3.0/

Changelog: https://pulp-rpm.readthedocs.io/en/latest/changes.html#id1
Docs: https://pulp-rpm.readthedocs.io/
Python bindings: https://pypi.org/project/pulp-rpm-client/3.3.0/

Ruby bindings: https://rubygems.org/gems/pulp_rpm_client/versions/3.3.0/

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

Re: [Pulp-list] pulpcore 3.3.0 and pulp_file 0.3.0 are Generally Available

2020-04-23 Thread Ina Panova
Correction, latest pulp_container release 1.3.0 is compatible with pulpcore
3.3.0



Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."


On Thu, Apr 23, 2020 at 6:15 PM Ina Panova  wrote:

> pulp_container 1.3.0 is released with the set of new features and
> bugfixes. It is also compatible with pulpcore 3.1.
>
> https://pulp-container.readthedocs.io/en/latest/changes.html#id1
> https://pypi.org/project/pulp-container/1.3.0/
> 
> Regards,
>
> Ina Panova
> Senior Software Engineer| Pulp| Red Hat Inc.
>
> "Do not go where the path may lead,
>  go instead where there is no path and leave a trail."
>
>
> On Thu, Apr 16, 2020 at 5:34 PM Mike DePaulo 
> wrote:
>
>> Here is another highlight for pulp_installer 3.3.0 [1]:
>>  * Added support for RHEL8 & CentOS 8 [2]
>>
>> [1] https://github.com/pulp/pulp_installer/releases/tag/3.3.0
>> [2] https://pulp.plan.io/issues/6259
>>
>> On Thu, Apr 16, 2020 at 10:04 AM Tatiana Tereshchenko <
>> ttere...@redhat.com> wrote:
>>
>>> Pulpcore 3.3.0 [0] and pulp_file 0.3.0 [1] have been released. For a
>>> list of all changes, please check the changelogs for pulpcore [2] and
>>> pulp_file [3]. Here are some highlights:
>>>  * Import/export of repository versions (tech preview)
>>>  * Repository version repairing (tech preview) [4]
>>>  * S3 is now fully supported and no longer a tech preview
>>>  * Various bugfixes and performance improvements
>>>
>>> The only backwards incompatible change [5] is:
>>>  * Exporting now requires ALLOWED_EXPORT_PATHS setting.
>>>
>>> # Installation and Upgrade
>>>
>>> Users should use the 3.3.0 release of pulp_installer (previously known
>>> as ansible-pulp) [6] to install or upgrade their installations. This
>>> version of the installer will check compatibility of all installed plugins
>>> with pulpcore 3.3. The installer will abort if any plugin is incompatible.
>>>
>>> # Plugin API
>>>
>>> Plugin writers can see the plugin API changelog here [7].
>>> There were a couple backwards incompatible changes [8]:
>>>  * One is about Exporter (you are not affected unless you have already
>>> started integrating with it).
>>>  * The other one makes it the responsibility of a plugin to check the
>>> duplicated content in a repository version. Pulpcore provides validation
>>> methods to do so. See the pulp_file example [9].
>>>
>>> And in keeping with the recommended strategy to pin plugins to a 3.y
>>> version of pulpcore, plugins should release compatibility releases with 3.3
>>> as soon as they can. We recommend using "pulpcore>=3.3,<3.4".
>>>
>>> [0] https://pypi.org/project/pulpcore/3.3.0/
>>> [1] https://pypi.org/project/pulp-file/0.3.0/
>>> [2] https://docs.pulpproject.org/changes.html#id1
>>> [3] https://pulp-file.readthedocs.io/en/0.3.0/changes.html#id1
>>> [4]
>>> https://docs.pulpproject.org/workflows/repairing-repository-versions.html
>>> [5] https://docs.pulpproject.org/changes.html#deprecations-and-removals
>>> [6] https://github.com/pulp/pulp_installer/releases/tag/3.3.0
>>> [7] https://docs.pulpproject.org/en/3.3.0/changes.html#plugin-api
>>> [8] https://docs.pulpproject.org/changes.html#id50
>>> [9]
>>> https://github.com/pulp/pulp_file/commit/dc6acb9d60a1d3aa61ff4def99cc12ddd9981076
>>> ___
>>> 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
>
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] pulpcore 3.3.0 and pulp_file 0.3.0 are Generally Available

2020-04-23 Thread Ina Panova
pulp_container 1.3.0 is released with the set of new features and bugfixes.
It is also compatible with pulpcore 3.1.

https://pulp-container.readthedocs.io/en/latest/changes.html#id1
https://pypi.org/project/pulp-container/1.3.0/

Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."


On Thu, Apr 16, 2020 at 5:34 PM Mike DePaulo  wrote:

> Here is another highlight for pulp_installer 3.3.0 [1]:
>  * Added support for RHEL8 & CentOS 8 [2]
>
> [1] https://github.com/pulp/pulp_installer/releases/tag/3.3.0
> [2] https://pulp.plan.io/issues/6259
>
> On Thu, Apr 16, 2020 at 10:04 AM Tatiana Tereshchenko 
> wrote:
>
>> Pulpcore 3.3.0 [0] and pulp_file 0.3.0 [1] have been released. For a list
>> of all changes, please check the changelogs for pulpcore [2] and pulp_file
>> [3]. Here are some highlights:
>>  * Import/export of repository versions (tech preview)
>>  * Repository version repairing (tech preview) [4]
>>  * S3 is now fully supported and no longer a tech preview
>>  * Various bugfixes and performance improvements
>>
>> The only backwards incompatible change [5] is:
>>  * Exporting now requires ALLOWED_EXPORT_PATHS setting.
>>
>> # Installation and Upgrade
>>
>> Users should use the 3.3.0 release of pulp_installer (previously known as
>> ansible-pulp) [6] to install or upgrade their installations. This version
>> of the installer will check compatibility of all installed plugins with
>> pulpcore 3.3. The installer will abort if any plugin is incompatible.
>>
>> # Plugin API
>>
>> Plugin writers can see the plugin API changelog here [7].
>> There were a couple backwards incompatible changes [8]:
>>  * One is about Exporter (you are not affected unless you have already
>> started integrating with it).
>>  * The other one makes it the responsibility of a plugin to check the
>> duplicated content in a repository version. Pulpcore provides validation
>> methods to do so. See the pulp_file example [9].
>>
>> And in keeping with the recommended strategy to pin plugins to a 3.y
>> version of pulpcore, plugins should release compatibility releases with 3.3
>> as soon as they can. We recommend using "pulpcore>=3.3,<3.4".
>>
>> [0] https://pypi.org/project/pulpcore/3.3.0/
>> [1] https://pypi.org/project/pulp-file/0.3.0/
>> [2] https://docs.pulpproject.org/changes.html#id1
>> [3] https://pulp-file.readthedocs.io/en/0.3.0/changes.html#id1
>> [4]
>> https://docs.pulpproject.org/workflows/repairing-repository-versions.html
>> [5] https://docs.pulpproject.org/changes.html#deprecations-and-removals
>> [6] https://github.com/pulp/pulp_installer/releases/tag/3.3.0
>> [7] https://docs.pulpproject.org/en/3.3.0/changes.html#plugin-api
>> [8] https://docs.pulpproject.org/changes.html#id50
>> [9]
>> https://github.com/pulp/pulp_file/commit/dc6acb9d60a1d3aa61ff4def99cc12ddd9981076
>> ___
>> 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
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

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

2020-04-23 Thread Dennis Kliban
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) <
bli...@bloomberg.net> 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 'HTTP_REMOTE_USER'
> ALLOWED_IMPORT_PATHS []
> PROFILE_STAGES_API False
> SWAGGER_SETTINGS {'DEFAULT_AUTO_SCHEMA_CLASS':
> 'pulpcore.app.openapigenerator.PulpAutoSchema',
> 'DEFAULT_GENERATOR_CLASS':
> 'pulpcore.app.openapigenerator.PulpOpenAPISchemaGenerator',
> 'DEFAULT_INFO': 'pulpcore.app.urls.api_info'}
> REDOC_SETTINGS {'SPEC_URL':
> '/pulp/api/v3/docs/?format=openapi_html=1'}
> CONTENT_ORIGIN 'http://myhost.bloomberg.com'
> SETTINGS '/etc/pulp/settings.py'
>
> Here is the log. gunicorn seems take the remote_user
> Apr 22 09:18:58 ip-1-76-158-49 gunicorn[12150]: pulp:
> django.request:WARNING: Forbidden: /pulp/api/v3/remotes/rpm/rpm/
> Apr 22 09:18:58 ip-1-76-158-49 gunicorn[12150]: 127.0.0.1 - bli4
> [22/Apr/2020:13:18:58 +] "GET /pulp/api/v3/remotes/rpm/rpm/ HTTP/1.0"
> 403 58 "-" "HTTPie/0.9.4"
> Apr 22 09:19:01 ip-1-76-158-49 systemd[1]: Created slice User Slice of
> root.
> Apr 22 09:19:01 ip-1-76-158-49 systemd[1]: Started Session 324743 of user
>