#32: Source code syntax highlight support in ovirt.org MediaWiki
-------------------------------+-----------------------------
Reporter: vszocs | Owner: infra@…
Type: enhancement | Status: new
Priority: trivial | Milestone: Handwavy Future
Component: wiki (MediaWiki) | Version:
Severity: Trivial | Keywords:
Blocked By: | Blocking:
-------------------------------+-----------------------------
It would be great if MediaWiki that powers ovirt.org supported source code
syntax highlighting. This would improve readability of wiki pages that
include source code snippets in various languages or formats.
The easiest way to do this is via MediaWiki extensions, e.g.
http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi.
--
Ticket URL: <https://fedorahosted.org/ovirt/ticket/32>
ovirt <http://www.ovirt.org/>
oVirt - virtualization made easy.
#17: Backups - what, where, when
-----------------------+------------------------
Reporter: quaid | Owner: infra@…
Type: task | Status: new
Priority: critical | Milestone: oVirt 3.2
Component: General | Version: Production
Severity: High | Keywords:
Blocked By: | Blocking:
-----------------------+------------------------
We need to work out solutions for:
* OpenShift backup
* Other servers
* Where can backups live?
* What can be backed-up on borrowed community space?
* What should be encrypted
--
Ticket URL: <https://fedorahosted.org/ovirt/ticket/17>
ovirt <http://www.ovirt.org/>
oVirt - virtualization made easy.
#31: Licensing (rights) link disappears when graphic is not used
-------------------------------+-----------------------
Reporter: quaid | Owner: infra@…
Type: task | Status: new
Priority: critical | Milestone: oVirt 3.2
Component: wiki (MediaWiki) | Version: Test
Severity: Trivial | Keywords:
Blocked By: | Blocking:
-------------------------------+-----------------------
I removed the incorrect-usage-of-a-trademark Apache logo from the footer
that was being used to link to the [[Licensing]] page of the wiki.
According to http://www.mediawiki.org/wiki/Manual:$wgRightsText just
having text there should make it appear as the text for the $wgRightsPage
and show $wgRightsUrl. If there is no $wgRightsText set, it should revert
to just showing the $wgRightsPage or $wgRightsUrl.
--
Ticket URL: <https://fedorahosted.org/ovirt/ticket/31>
ovirt <http://www.ovirt.org/>
oVirt - virtualization made easy.
#39: Upgrade MediaWiki Strapping theme
-------------------------------+-----------------------------
Reporter: quaid | Owner: infra@…
Type: task | Status: new
Priority: major | Milestone: Handwavy Future
Component: wiki (MediaWiki) | Version: Test
Severity: Trivial | Keywords:
Blocked By: | Blocking:
-------------------------------+-----------------------------
Upstream has a few changes that may resolve some of our tickets.
Regardless, we can't troubleshoot our tickets against the upstream unless
we upgrade.
https://github.com/OSAS/strapping-mediawiki
--
Ticket URL: <https://fedorahosted.org/ovirt/ticket/39>
ovirt <http://www.ovirt.org/>
oVirt - virtualization made easy.
Hi guys,
it would be great if MediaWiki that powers ovirt.org supported source code syntax highlighting. This would improve readability of wiki pages that include source code snippets in various languages or formats.
I've created a Trac ticket for this: https://fedorahosted.org/ovirt/ticket/32
Thanks!
Vojtech
#41: reject gerrit posts with invalid Bug-Url
----------------------+-----------------------
Reporter: danken | Owner: infra@…
Type: task | Status: new
Priority: major | Milestone: oVirt 3.3
Component: General | Version:
Severity: Normal | Keywords:
Blocked By: | Blocking:
----------------------+-----------------------
It is all to common for people to post patches with a comment that
includes a broken or private Bug-Url: label.
gerrit should block such posts on entry. There should be a hook that
verifies that the URL is of a valid form, and that the referred bug is
public. Since accessing bugzilla may be a bit slow, we may need to do this
asynchronously, and give a -1 to such a post.
In my opinion, the only valid form should be
Bug-Url: https://bugzilla.redhat.com/926954
But others prefer to also allow
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=926954
Bug-Id or buG-url should be rejected, too.
--
Ticket URL: <https://fedorahosted.org/ovirt/ticket/41>
ovirt <http://www.ovirt.org/>
oVirt - virtualization made easy.
Hi,
I am adding new upgrade job for engine. I need ssh access to jenkins slaves
to debug the job. What is the process for getting ssh access ?
Thanks,
Kiril Nesenko
Red Hat, Inc.
www.redhat.com
fyi,
i've successfully installed a new ovirt-engine 3.2.1 instance running on alterway02.ovirt.org (centos).
admin password is located in resources.ovirt.org/root/passwords.
it's running 'all in one' setup, which means the alterway02 bare metal server is acting both as engine & host.
WHAT'S NEXT?
- loading an iso file (centos?) to the host and installing a 1st basic centos vm
(looking forward we'll probably use foreman as pxe/tftp server for installing vms)
- creating a template from that vm for future use
- now we need to decide which 1st infra vm we want to install (resources/gerrit/foreman?)
- what are the needed specs? (space/mem/cpu)
I'm guessing we'd want to give the instance a proper fqdn -> "manager01.ovirt.org", "engine.ovirt.org" ?
thoughts, idea?
Eyal.
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2LSQILQBWBPOVSLGXPWVB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
We can get an SSL cert for each subdomain, or we can get a wildcard
cert. My understanding is that it is more secure to use one-per-subdomain=
=2E
Presuming we want the one-per model, what are the subdomains we need to
get a cert for?
gerrit.ovirt.orgjenkins.ovirt.orgresources.ovirt.orgforeman.ovirt.orgsmartproxy.ovirt.orglists.ovirt.org
- Karsten
--=20
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
http://TheOpenSourceWay.org .^\ http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
------enig2LSQILQBWBPOVSLGXPWVB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iD8DBQFRUx+Y2ZIOBq0ODEERAsogAKDO9sFbEdGWdPPMjyAg7iPCT/MLbgCgzgBR
SCyRWznhka2L0XZFV+ijRfI=
=/NZ/
-----END PGP SIGNATURE-----
------enig2LSQILQBWBPOVSLGXPWVB--
Next week is easter so I'm not sure about if everyone can attend. During
the meeting I got the following responses. Please add/correct where
possible.
Rydekull likely
ewoud likely
quaid unsure
dneary no
dcaro no
Though I'm sure Rydekull and I can have a very nice meeting, it may
better to move it if it turns out it's just the two of us.
