Re: [ovirt-users] [ovirt-devel] Lowering the bar for wiki contribution?
by Roy Golan
Adding infra which I forgot to add from the beginning
On 7 January 2017 at 02:44, Jakub Niedermertl <jniederm(a)redhat.com> wrote:
> On Wed, Jan 4, 2017 at 11:41 AM, Roy Golan <rgolan(a)redhat.com> wrote:
> >
> >
> > On 4 January 2017 at 12:17, Maor Lipchuk <mlipchuk(a)redhat.com> wrote:
> >>
> >>
> >>
> >> On Wed, Jan 4, 2017 at 11:38 AM, Daniel Erez <derez(a)redhat.com> wrote:
> >>>
> >>>
> >>>
> >>> On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan <rgolan(a)redhat.com> wrote:
> >>>>
> >>>> I'm getting the feeling I'm not alone in this, authoring and
> publishing
> >>>> a wiki page isn't as used to be for long time.
> >>>>
> >>>> I want to suggest a bit lighter workflow:
> >>>>
> >>>> 1. Everyone can merge their page - (it's a wiki)
> >>>> Same as with (public and open) code, no one has the motivation to
> >>>> publish a badly written
> >>>> wiki page under their name. True, it can have an impact, but not as
> >>>> with broken code
> >>>>
> >>>
> >>> +1.
> >>> Moreover, I think we shouldn't block any merging. Instead, wiki
> >>> maintainers could act afterwards and revert when needed (Wikipedia
> style).
> >>> Another issue is that (sadly) unlike mediawiki, we need to wait for
> wiki
> >>> publish after a change. So I'd suggest to build and publish the wiki at
> >>> least once a day. Any way, I think we should make the workflow much
> more
> >>> intuitive and pleasant like the previous wiki - i.e. much less
> restrictive
> >>> than manipulating a code base.
> >>>
> >>>
> >>>>
> >>>> 2. Use Page-Status marker
> >>>> The author first merges the draft. Its now out there and should be
> >>>> updated as time goes and its
> >>>> status is DRAFT. Maintainers will come later and after review would
> >>>> change the status to
> >>>> PUBLISH. That could be a header in on the page:
> >>>> ---
> >>>> page status: DRAFT/PUBLISH
> >>>> ---
> >>>>
> >>>> Simple I think, and should work.
> >>>>
> >>
> >> +1
> >> The effort of maintaining the wiki today compare to how it used to be
> >> before is much more cumbersome and problematic.
> >> I think we can learn a lot from wikipedia workflow,
> >> It is a much more inviting process where anyone can change the content
> >> easily.
> >> I'm not saying we should let any anonymous user change the wiki but even
> >> if we make it easier in house we can achieve much more informative
> reliable
> >> and updated wiki.
> >>
> >
> >
> >
> > I really think Github Pages is a perfect fit and an alternative to my
> first
> > suggestion. see
> > https://github.com/oVirt/ovirt-site/wiki/Why-aren't-we-using-this%3F
>
> +1
> Github wiki would allow us instant publishing, review after after
> publishing, it works purely in browser (no need for running local ruby
> server) and it's a service that doesn't require any maintenance form
> our side.
>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Devel mailing list
> >>>> Devel(a)ovirt.org
> >>>> http://lists.ovirt.org/mailman/listinfo/devel
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users(a)ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>>
> >>
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
7 years, 5 months
[ OST Failure Report ] [ oVirt master ] [ 31.01.2017 ] [add_secondary_storage_domains]
by Evgheni Dereveanchin
Test failed: add_secondary_storage_domains
Links to suspected patches:
https://gerrit.ovirt.org/71376
https://gerrit.ovirt.org/71427
https://gerrit.ovirt.org/71345
Link to Job:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5040/
Link to all logs:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5040/art...
Error snippet from log:
2017-01-31 05:54:53,862-0500 ERROR (jsonrpc/5) [storage.TaskManager.Task] (Task='ad8f48fc-de09-4c26-b052-7a036d7651ad') Unexpected error (task:871)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 878, in _run
return fn(*args, **kargs)
File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/storage/hsm.py", line 2215, in getAllTasksInfo
allTasksInfo = self._pool.getAllTasksInfo()
File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper
raise SecureError("Secured object is not in safe state")
SecureError: Secured object is not in safe state
Regards,
Evgheni Dereveanchin
7 years, 9 months
oVirt infra daily report - unstable production jobs - 217
by jenkins＠jenkins.phx.ovirt.org
------=_Part_303_764736849.1485903614587
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Good morning!
Attached is the HTML page with the jenkins status report. You can see it also here:
- http://jenkins.ovirt.org/job/system_jenkins-report/217//artifact/exported...
Cheers,
Jenkins
------=_Part_303_764736849.1485903614587
Content-Type: text/html; charset=us-ascii; name=upstream_report.html
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=upstream_report.html
Content-ID: <upstream_report.html>
<!DOCTYPE html><head><style type="text/css">
table.gridtable {
border-collapse: collapse;
table-layout:fixed;
width:1600px;
font-family: monospace;
font-size:13px;
}
.head {
font-size:20px;
font-family: arial;
}
.sub {
font-size:18px;
background-color:#e5e5e5;
font-family: arial;
}
pre {
font-family: monospace;
display: inline;
white-space: pre-wrap;
white-space: -moz-pre-wrap !important;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;
}
</style>
</head>
<body>
<table class="gridtable" border=2>
<tr><th colspan=2 class=head>
RHEVM CI Jenkins Daily Report - 31/01/2017
</th></tr><tr><th colspan=2 class=sub>
<font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font>
</th></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el...">ovirt-live_master_experimental_create-iso-el7-x86_64</a>
</td><td>
<h3>This job generates a nightly iso of ovirt-live using experimental repos</h3>
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_buil...">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x...">ovirt-system-tests_master_check-patch-fc24-x86_64</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/">test-repo_ovirt_experimental_4.1</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_303_764736849.1485903614587--
7 years, 9 months
[JIRA] (OVIRT-1093) Re: Repository request
by eyal edri [Administrator] (oVirt JIRA)
eyal edri [Administrator] created OVIRT-1093:
------------------------------------------------
Summary: Re: Repository request
Key: OVIRT-1093
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1093
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: eyal edri [Administrator]
Assignee: infra
On Jan 31, 2017 18:13, "Fabian Deutsch" <fdeutsch(a)redhat.com> wrote:
> Hey,
>
> could you please create the following repository on gerrit:
>
> ovirt-on-kubevirt.git
>
> This repository can documentation, diagrams, and a demo of how ovirt
> can consume KubeVirt.
>
> - fabian
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
--
This message was sent by Atlassian JIRA
(v1000.718.4#100026)
7 years, 9 months
Repository request
by Fabian Deutsch
Hey,
could you please create the following repository on gerrit:
ovirt-on-kubevirt.git
This repository can documentation, diagrams, and a demo of how ovirt
can consume KubeVirt.
- fabian
7 years, 9 months
[JIRA] (OVIRT-1092) test-repo_ovirt_experimental_4.1 - chown error when publishing repo
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1092?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1092:
-------------------------------------
The files under '/srv/resources/repos/ovirt/tested/4.1' were root-owned for some reason.
I created the 4.1 repo manually (as opposed to letting the script do it), so perhaps I did it as root instead of 'deploy-ovirt-experimental' without notice. I can't tell from the history.
In any case I chowned the files no, so if should be ok from now on.
Next time please ping me on IRC immediately on OST issues instead of waiting for me to notice the ticket. Its a shame because we now have to log 16! failed OST runs as infra issues for something that takes less then a second to fix.
> test-repo_ovirt_experimental_4.1 - chown error when publishing repo
> -------------------------------------------------------------------
>
> Key: OVIRT-1092
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1092
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
> Reporter: Evgheni Dereveanchin
> Assignee: infra
> Priority: High
>
> test-repo_ovirt_experimental_4.1 is failing without visible errors on lago side.
> Checking job logs, there's the following error when publishing RPMs:
> 12:24:49 Copying to published repo
> 12:24:49 + echo 'Copying to published repo'
> 12:24:49 + install -o deploy-ovirt-experimental -m 755 -d /srv/resources/repos/ovirt/tested/4.1
> 12:24:49 install: cannot change owner and permissions of ‘/srv/resources/repos/ovirt/tested/4.1’: Operation not permitted
> 12:24:49 + rm -f /home/deploy-ovirt-experimental/experimental_repo.lock
> [Pipeline] } //sshagent
> [Pipeline] SSH Agent : End
> [Pipeline] } //wrap
> [Pipeline] General Build Wrapper : End
> [Pipeline] } //node
> [Pipeline] Allocate node : End
> [Pipeline] End of Pipeline
> ERROR: script returned exit code 1
> Finished: FAILURE
> There was no "install" command in logs before builds started failing
> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/436/console
--
This message was sent by Atlassian JIRA
(v1000.718.4#100026)
7 years, 9 months
