GithubHelp home page GithubHelp logo

ovirt / ovirt-site Goto Github PK

View Code? Open in Web Editor NEW
86.0 26.0 290.0 1.04 GB

oVirt website

Home Page: http://www.ovirt.org/

License: Other

Ruby 14.57% Shell 3.37% HTML 4.25% JavaScript 0.92% CSS 5.17% CoffeeScript 1.52% Haml 14.17% Sass 50.15% SCSS 0.53% Dockerfile 0.96% Python 4.39%
ovirt ovirt-website virtualization

ovirt-site's People

Contributors

abonas avatar alonakaplan avatar alonbl avatar assafmuller avatar bproffitt avatar bronhaim avatar danielerez avatar dankenigsberg avatar didib avatar dougsland avatar emarcusrh avatar emesika avatar fabiand avatar ffromani avatar garrett avatar gregsheremeta avatar jhernand avatar johnmarksrh avatar lveyde avatar masayag avatar mburns72h avatar mureinik avatar mwperina avatar oourfali avatar quaid avatar rgolangh avatar sabose avatar sandrobonazzola avatar sradco avatar xsgordon avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ovirt-site's Issues

Review & optimize code blocks

Many pages use code blocks. This issue addresses the need to review and optimize each code block. Optimized code blocks are indented starting at the flush left, surrounded by three backticks and, optionally, the programming language (which would cause the code block to be syntax highlighted)... instead of just merely being indented.

See http://kramdown.gettalong.org/syntax.html#code-blocks for more information.

Please note that we do not use the fenced code block style as in the Kramdown documentation, but use GitHub-style fenced code blocks (that is, backticks '`' instead of tildes '~').

See https://help.github.com/articles/github-flavored-markdown/#fenced-code-blocks

(Note: We basically use GitHub style Markdown with a bit of Kramdown enhancements on top. This is so we can preview most everything on GitHub directly and still can use classes and such with {:.classnameone.classnametwo} type Kramdown extensions.)

Expand community guidelines topic to community CoC

Currently we have a "community guidelines" topic that lists in general terms the guidelines to follow when operating within the community. However, the topic describes conduct guidelines only in broad terms, and also contains sections related to naming conventions etc, that don't really belong there.

Link to original topic:
https://github.com/oVirt/ovirt-site/blob/master/source/community/about/community-guidelines.html.md

Need to break down the topic to conduct vs infra vs ops, and formalize each type of information into its own topic.

Add "Blog" tab in top navbar and switch Develop/Community tabs

The Blog tab should link to a page that contains the "archives" of the blog posts (same page that is accessible when you click "more news" from the Home page).

After the reorg, the top navbar should read:

Home
Blog
Download
Documentation
Develop
Community
Search

Add URL fragments as search keywords

Since a 404 triggers a search of pages, it's probably useful to add the search fragments to the search index.

In most cases, the page bubbles to the top anyway, but in a few somewhat rare instances, the terms are only used in the URL and not in the page, making the 404 search show no results. Adding the fragments to the index, both for the original page as well as a wiki title (if applicable), would ensure the page would show up in these cases.

"Jobs" section

oVirt is always looking for talented contributors. Red Hat may be able to hire some of them. Please add a "Jobs" tab to the main page, where we can list the descriptions of Linux-savvy Python and enterprise Java developers that we are looking for.

Inaccurate ovirt engine picture in architecture page

In the new architecture page (http://www.ovirt.org/documentation/architecture/architecture/), overall architecture picture shows that engine supports active-active high availability.

According to Yaniv Kaul(ykaul at redhat.com) in mailing list,

This is inaccurate - the engine is not highly available in A/A
architecture. I'd appreciate if you could file an issue for it so we'll fix
this page.

(copy-paste from https://bugzilla.redhat.com/show_bug.cgi?id=1315120 )

automatic page-level "table of contents" menus

In the old site, many/most pages had "Contents" automatically generated based on their internal section/subsection hierarchy. IMO we should have that by default for most pages of the new site, perhaps with a simple option to turn off/on. I searched a bit and could not find how to do that and/or whether it's supposed to be supported.

As an example, compare these:

http://old.ovirt.org/Hosted_Engine_Howto

https://www.ovirt.org/documentation/how-to/hosted-engine/

In addition, sections/subsections should be links to themselves, e.g. the title "Migrate existing setup to a VM", both in the menu and in the body, should be a link to the already-working URL:

https://www.ovirt.org/documentation/how-to/hosted-engine/#migrate-existing-setup-to-a-vm

(And, BTW, it will be nice if pressing this link will open it with the section title below the top bar, instead of being covered by it, as it is now at least for me (firefox 45)).

Local test requested before pull, but no instructions and both server and docker scripts fail

Hi,

The CONTRIBUTING file asks for local testing of changes in the "Test your changes locally" section. But there are no instructions about how to actually do that.

I tried using the standard approach of bundle install && bundle exec ./run-server.sh, but it fails with:

/home/msivak/.gem/ruby/gems/middleman-core-3.3.10/lib/middleman-core/core_extensions/data.rb:167:in `method_missing': undefined method `events' for #<Middleman::CoreExtensions::Data::DataStore:0x00000004b30160> (NoMethodError)
    from /home/msivak/Work/ovirt-site/config.rb:138:in `block in initialize'

I also tried to use the ./docker-setup.sh && ./docker-run.sh script, but that also failed:

[msivak@dhcp131-31 ovirt-site]$ sudo ./docker-run.sh 
Running docker image springboard-20160420-10023
An error occurred while installing nokogiri (1.6.6.2), and Bundler cannot
continue.
Make sure that `gem install nokogiri -v '1.6.6.2'` succeeds before bundling.

So apart from having no instructions, the "obvious" ways do not work either.

Move feature pages

Feature pages should be created in /source/develop/features/, and at the moment they're in /source/feature/. The feature template should also be moved there.

slide-decks.html.md - broken links

Links to documents in ovirt.org slide decks page are broken, as they point to documents uploaded to old images/ or wp-content/upload folders, which aren't available anymore.
Are these ODPs and PDFs migrated to the new site - can't find them in git repository...

Previous site pages are unreachable

Even if from the new website the previous website page are referenced, they're not reachable anymore so if something gone wrong with the conversion you can't reach the correct one to compare with.

Admin guide markup corrupts 1/3 of guide

The markup after 'Installing Guest Agents and Drivers' corrupts the remainder of the document. Looks like there is some html that is not parsed by the markdown engine and breaks everything afterwards.

This is the raw code where it breaks. I notice it renders properly on github just not on the web site.

Installing the agents and drivers on Red Hat Enterprise Linux guests
All of the drivers are included in the base channel for RHN-registered Red Hat Enterprise Linux virtual machines. They can be installed using the `yum install rhevm-guest-agent` command. Your RHEL guest must be subscribed to the `Red Hat Enterprise Virt Agent` channel to install the agents. In Red Hat Enterprise Linux 5, this channel is labeled `rhel-x86_64-rhev-agent-5-server`. In Red Hat Enterprise Linux 6, the channel is labeled `rhel-x86_64-rhev-agent-6-server`.
Installing the agents and drivers on Windows guests
The guest tools ISO is `ovirt-guest-tools-iso.rpm`, an RPM file installed on oVirt. After installing oVirt, the guest tools ISO can be found at `/usr/share/rhev-guest-tools-iso/ovirt-tools-setup.iso`. When setting up oVirt, if you have created a local storage share for an ISO storage domain, the ISO file is automatically copied to the ISO storage domain. In this case the ISO image is automatically attached to Windows guests when they are created. Otherwise, the ISO must be manually attached to Windows guests for the tools and agents to be installed. Updated versions of the ISO file must be manually attached to running Windows virtual machines to install updated versions of the tools and drivers. If the APT service is enabled on virtual machines, the updated ISO files will be automatically attached.
##### Automating Guest Additions on Windows Guests with oVirt Application Provisioning Tool(APT)

oVirt Application Provisioning Tool (APT) is a Windows service that can be installed in Windows virtual machines and templates. Attach the guest tools ISO file to your Windows virtual machine and ovirt-Application Provisioning.exe automatically runs to install the APT service.

When the APT service is installed on a virtual machine, attached ISO files are automatically scanned. When the service recognizes a valid oVirt guest tools ISO, and no other guest tools are installed, the APT service installs the guest tools. If guest tools are installed, and the ISO image contains newer versions of the tools, an upgrade is automatically performed.

When the APT service has successfully installed or upgraded guest tools on a virtual machine, the virtual machine is automatically rebooted.

oVirt Guest Drivers and Guest Agents

oVirt provides customized drivers and guest tools to use with Windows and Red Hat Enterprise Linux guests. The drivers allow guests to use enhanced virtual devices that perform better than emulated devices; the guest agents facilitate communication between the guest and oVirt.

Table 8.15. oVirt Guest Drivers

Driver

Description

Works on

virtio-net

Paravirtualized network driver provides enhanced performance over emulated devices like rtl.

Server and Desktop.

virtio-block

Paravirtualized HDD driver offers increased I/O performance over emulated devices like IDE by optimizing the coordination and communication between the guest and the hypervisor. The driver complements the software implementation of the virtio-device used by the host to play the role of a hardware device.

Server and Desktop.

virtio-scsi

Paravirtualized iSCSI HDD driver offers similar functionality to the virtio-block device, with some additional enhancements. In particular, this driver supports adding hundreds of devices, and names devices using the standard SCSI device naming scheme.

Server and Desktop.

virtio-serial

Virtio-serial provides support for multiple serial ports. The improved performance is used for fast communication between the guest and the host that avoids network complications. This fast communication is required for the guest agents and for other features such as clipboard copy-paste between the guest and the host and logging.

Server and Desktop.

virtio-balloon

Virtio-balloon is used to control the amount of memory a guest actually accesses. It offers improved memory over-commitment. The balloon drivers are installed for future compatibility but not used by default in oVirt 3.1 or higher.

Server and Desktop.

qxl

A paravirtualized display driver reduces CPU usage on the host and provides better performance through reduced network bandwidth on most workloads.

Server and Desktop.

Table 8.16. oVirt Guest Agents and Tools

Guest agent/tool

Description

Works on

ovirt-guest-agent

Allows oVirt to receive guest internal events and information such as IP address and installed applications. Also allows oVirt to execute specific commands, such as shut down or reboot, on a guest. On Red Hat Enterprise Linux 6 and higher guests, the ovirt-guest-agent installs tuned on your virtual machine and configures it to use an optimized, virtualized-guest profile.

Server and Desktop.

spice-agent

The SPICE agent supports multiple monitors and is responsible for client-mouse-mode support to provide a better user experience and improved responsiveness than the QEMU emulation. Cursor capture is not needed in client-mouse-mode. The SPICE agent reduces bandwidth usage when used over a wide area network by reducing the display level, including color depth, disabling wallpaper, font smoothing, and animation. The SPICE agent enables clipboard support allowing cut and paste operations for both text and images between client and guest, and automatic guest display setting according to client-side settings. On Windows guests, the SPICE agent consists of vdservice and vdagent.

Server and Desktop.

ovirt-sso

An agent that enables users to automatically log in to their virtual machines based on the credentials used to access oVirt.

Desktop.

ovirt-usb

A component that contains drivers and services for Legacy USB support (version 3.0 and earlier) on guests. It is needed for accessing a USB device that is plugged into the client machine. ovirt-USB Client is needed on the client side.

Desktop.

Release notes conversion is incomplete

Comparing http://www.ovirt.org/release/3.6.3/ and OVirt_3.6.3_Release_Notes I mirrored locally before the switch to the new site, I see that the table of contents is missing (just annoying) and all references to the bugs have been lost (real issue).

In older site I had:

  • BZ 1191514 - Missing gluster error codes

with the BZ linked to the bugzilla url. It used a macro/template {{BZ|1191514}}
in new site I only see:

  • Missing gluster error codes

Can this be fixed?

Events are broken: both Upcoming & /events/

  • the /events/ page has moved elsewhere; this should be corrected
  • check to see if events are being picked up properly, and why they're not showing up
  • ensure events are tagged with oVirt in rh-events
  • port over event changes from RDO wiki conversion to middleman

Fix search hash escaping

Under some circumstances, the hash in the URI might have encoding. Example: %20 instead of a space.

old.ovirt.org indexed

Now noticed that a google search returned also results from old.ovirt.org.

If we intend to drop it by end of current month, which btw seems
pretty immature to me - perhaps wait half a year or so, we better stop
google from searching and/or returning results from it. robots.txt
should have been enough if done beforehand, not sure what tools exist
now. Adding one won't hurt anyway. Obviously google has specific tools
for webmasters, we probably want if possible something general for
many search engines.

Already reported to infra mailing list [1], as most of not all of the above is hardly relevant to the new site. Opening also this issue per Mikey's request.

[1] http://lists.ovirt.org/pipermail/infra/2016-March/013636.html

Customize README.md

The readme file should be customized to be specifically for oVirt.

  • The title of README.md should reflect oVirt.
  • If directions do not work or need to be expanded upon, those should also be updated too.

Privacy policy of the project is inadequate

Since @thatdocslady did ask me for a new bug report, let's restart the discussion from #3 here.

So basically, the reuse of the RH privacy policy is inadequate for ovirt.org for several reasons, and i will list just the 2 main ones for now to not overload the issue:

First, it states that RH do not give the information except to partner that signed a confidentiality agreement, law enforcement or in case of merger/acquisition.

Since we have community members who would have access to various informations, we are already breaching the privacy policy, and I think it should be amended, like did the one of Fedora.

Second point, the part about remarketing is something we are not doing, and there is people who would see that weird, me being the first.

So I think we should first have a list of our existing practice regarding private informations, then see which one we are supposed to do or not, and the impact. Then once we have this, we can go to Legal see what can be done to fix the policy to make it correspond to what we do, or if we need to stop doing something (example, logwatch on public list).

First blog post

We need an actual blog post with content. The site doesn't look right without it.

It would be nice to get this in soon, or at least have a filler post so the layout isn't broken*. (:

(* The site should never have empty blog posts ever again, once it's deployed to production, so it's not a problem.)

No breadcumbs

the only way to navigate back is hitting the back button, in the wiki you have some hirachized breadcumbs links that help navigating topics

Failure to setup - as zlib-devel RPM is missing

Fedora 23, with all updates.

Running: sudo ./setup.sh

ends with:
Using erubis 2.7.0
Installing expression_parser 0.9.0
Installing favicon_maker 1.3
Installing mini_portile 0.6.0

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

/usr/bin/ruby -r ./siteconf20151214-31202-1lbjeh2.rb extconf.rb 

checking if the C compiler accepts ... yes
Building nokogiri using packaged libraries.
checking for gzdopen() in -lz... no
zlib is missing; necessary for building libxml2
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.

Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib64
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/$(RUBY_BASE_NAME)
--help
--clean
--use-system-libraries
--enable-static
--disable-static
--with-zlib-dir
--without-zlib-dir
--with-zlib-include
--without-zlib-include=${zlib-dir}/include
--with-zlib-lib
--without-zlib-lib=${zlib-dir}/lib64
--enable-cross-build
--disable-cross-build

extconf failed, exit code 1

Gem files will remain installed in /usr/local/share/gems/gems/nokogiri-1.6.6.2 for inspection.
Results logged to /usr/local/lib64/gems/ruby/nokogiri-1.6.6.2/gem_make.out
An error occurred while installing nokogiri (1.6.6.2), and Bundler cannot
continue.
Make sure that gem install nokogiri -v '1.6.6.2' succeeds before bundling.


The gem mentioned above fails to install as zlib-devel RPM is missing.

scrub pages pertaining to MediaWiki

Many pages are out of date, simply by the fact that they contain MediaWiki-related information. The pages should either be:

  1. Removed
  2. Have MediaWiki information removed from the page (and leave other stuff)
  3. Changed to reflect similar Middleman-related information

Which method of the above that should be used really depends on the page in question.

To start, here's a search for "MediaWiki":

https://beta-ovirtweb.rhcloud.com/search/#mediawiki

...all of these pages should be looked at and corrected. You can, of course, click on the "Edit on GitHub" link on the bottom of the page if you see anything amiss on a page.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.