Re: [Pulp-list] Pulp 2.10.3 Beta 1 now available!

2016-11-23 Thread Sean Myers
On 11/21/2016 04:53 PM, Sean Myers wrote:
> Potential Known Issue
> =
> 
> Our el6 test suite was indicating that this release might be unstable for 
> that platform.
> We're investigating this now, and I'll update here once we know more.

dkliban determined that this was indeed broken. We've fixed the problem 
affecting el6
builds, and I've pushed the update up to the beta repositories.

Here's the issue, for reference:
https://pulp.plan.io/issues/2436

This issue will be included in the normal issue list for future release 
announcements
regarding 2.10.3.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.11.0 Beta 3 Now Available

2016-11-23 Thread Sean Myers
Pulp 2.11.0 Beta 3 is now available, and can be downloaded from
the 2.11 beta repositories:

https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.11/

A failing migration was discovered, preventing some users from upgrading from 
previous
versions of Pulp, and was fixed in Beta 2:

https://pulp.plan.io/issues/2377

Additionally, fixes included in the 2.10.2 hotfix release and 2.10.3 have been 
brought
forward to 2.11 Beta 3.

New features for Pulp 2.11 include more improvements to RPM syncing, the 
ability to pull older
trees with OSTree, incremental publish with Docker and RPM, and the ability to 
upload DRPMS.
Several bugs were also fixed; all the details can be found later in this 
announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.11/testing/user-guide/release-notes/2.11.x.html
http://docs.pulpproject.org/en/2.11/testing/plugins/pulp_rpm/user-guide/release-notes/2.11.x.html
Docker 2.2 and OSTree 1.2 release notes coming soon.

Try out the new features, and let us know how they work for you!


Upgrading
=

The 2.11 beta repositories are included in the pulp repo files:
https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 23 & 
24
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 6 & 7

After enabling the pulp-2.11-beta repository, you'll want to follow the standard
upgrade path, with migrations, to get to 2.11:

> $ sudo systemctl stop httpd pulp_workers pulp_resource_manager pulp_celerybeat
> $ sudo yum upgrade
> $ sudo -u apache pulp-manage-db
> $ sudo systemctl start httpd pulp_workers pulp_resource_manager 
> pulp_celerybeat


New Features


Here are the specific stories done for 2.11:

  Docker Support
2114As a user, I can perform incremental publish with Docker rsync 
distributor

  OSTree Support
2205As a user, I want to pull older versions of trees available to 
atomic hosts.

  Pulp
1983As a user, an importer config change or content removal will 
cause the next sync to be full
2172Memory Improvements with Process Recycling
2186As a user, pulp-manage-db refuses to run if other pulp 
processes are running locally

  RPM Support
1806As a user, I can use pulp-admin to upload drpms
2113As a user, I can perform an incremental publish using ISO rsync 
distributor
2132As a consumer of Pulp content I want ISO & ISO_rsync 
distributor to support relative_url for consistency with yum
2211As a user, I can sync a distribution unit with the existing 
yum_importer without requiring yum metadata
2212As a user I can see in the task report of copy operation list 
of units which did not pass signature filter 

View this list in redmine:
http://bit.ly/2eQz5Ui


Issues Addressed


Here are the bug fixes specific to 2.11:

  Pulp
23770025_importer_schema_change hits issue with last_sync being None
1977basic auth in URL fails when using authenticated proxy
1069extra Task ID in docs example to bind a repo
2133Permissions docs should include some info on /v2/
752 Suggestion to add -v remains even if you use -v

  RPM Support
2224Cannot sync from mirrorlists
2321Pulp can't handle mirrorlists with invalid entries
2363Pulp acts like all is well when a sync completely fails
2071Creating yum distributor without https, http keys in config 
crashes

All bug fixes from Pulp 2.10.3 and earlier are included in Pulp 2.11.

View this list in redmine:
http://bit.ly/2dHG8ws



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Hosting Live Sprint Demos?

2016-11-23 Thread Filip Dobrovolny
What about using YouTube + Hangouts On Air?

* allow for anyone to join the event live - It allows anyone to comment
live.
* support screensharing and video content from presenters - Supply screen
sharing and I think even playing videos from YT.
* provide recording - Automatically video is posted to YT.
* not use flash - HTML5 / Flash depends on user.
* automatically host those recorded videos in their forever home on the web
- It does. (2 points above)
* allow me to upload videos too, so that both live and pre-recorded videos
can be in one place - You can upload videos.
* support teams allowing several people to administrate it, not just me -
You can create Brand account and have YT channel with multiple managers.
* have no cost (for sustainability) - It's free, but it might require
non-redhat google accounts.
* provide analytics for both live attendance and viewing - I think so.



Kind Regards,

Filip Dobrovolny.

On Wed, Nov 23, 2016 at 3:04 AM, Brian Bouterse  wrote:

> Currently our sprint demos are recorded and don't allow for live
> participation from the community. In an effort to be more open, I would
> like to move our sprint demos to be a live, public event. To do that, I
> need to switch how we are recording and hosting the sprint demos.
>
> Do any of you have suggestions on what services I should consider?
>
> My ideal integrated hosting+playback environment would:
>
> * allow for anyone to join the event live
> * support screensharing and video content from presenters
> * provide recording
> * not use flash (at least not for playback)
> * automatically host those recorded videos in their forever home on the web
> * allow me to upload videos too, so that both live and pre-recorded videos
> can be in one place
> * support teams allowing several people to administrate it, not just me
> * have no cost (for sustainability)
> * provide analytics for both live attendance and viewing
>
> Feel free to reply on-list or directly with ideas or discussion.
>
> Thanks!
> Brian
>
>
>
> ___
> 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