Please don't remove instance type
by Baptiste Agasse
Hi all,
We are happy oVirt users for some years now (we started with 3.6, now on 4.2) and we manage most of our virtualization stacks with it. To provision and manage our machines, we use the foreman (for bare metal and virtual machines) on top of it. I made some little contributions to the foreman and other underlying stuff to have a deeper integration with oVirt, like to be able to select instance type directly from foreman interface/api and we rely on it. We use instance types to standardize our vms by defining system resources (memory, cpu and cpu topology) console type, boot options. On top of that we plan to use templates to apply OS (CentOS 7 and CentOS 6 actually). Having resources definitions separated from OS installation help us to keep instance types and templates lists small and don't bother users about some technical underlying stuff. As we are interested in automating oVirt maintenance tasks and configuration with ansible, I asked at FOSDEM oVirt booth if there is any ansible module to manage instance types in Ovirt as I didn't find it in ovirt ansible infra repo. The person to whom I asked the question said that you are planning to remove instance types from ovirt, and this make me sad :(. So here I am to ask why do you plan to remove instance types from oVirt. As far as I know, it's fairly common to have "instance types" / "flavors" / "sizes" on one side and then templates (bare OS, preinstalled appliances...) on other side and pick one of each to make an instance. If this first part is missing in future version of ovirt, it will be a pain point for us. So, my question is, do you really plan to remove instances type definitely ?
Cheers.
--
Baptiste
6 years
Taking down the engine without setting global maintenance
by Yedidyah Bar David
Hi all,
How about making this change:
Right before the engine goes down cleanly, it marks the shared storage
saying it did not crash but exited cleanly, and then HE-HA will not
try to restart it on another host. Perhaps make this optional, so that
users can do clean shutdowns and still test HA cleanly (or some other
use cases, where users might not want this).
This should help a lot cases where people restarted their engine for
some reason, e.g. upgrade, and forgot to set maintenance.
Makes sense?
--
Didi
6 years
getting a weird error when doing OST
by Ahmad Khiet
Hi,
I'm trying to run OST on a patch, but I'm getting the following error:
tried twice.. and I'm getting the same error :
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4221/console
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4206/console
Thanks,
Ahmad.
*10:06:27* *10:06:27* - STDERR*10:06:27* ++ uname -r*10:06:27*
++ awk -F. '{print $(NF-1)}'*10:06:27* + DIST=el7*10:06:27* +
FC_REGEX='^fc[0-9]+$'*10:06:27* + cat*10:06:27* + cat*10:06:27* ++ ip
route*10:06:27* ++ awk '$1=="default" {print $5; exit}'*10:06:27* +
NIC=eth0*10:06:27* ++ /sbin/ip -4 -o addr show dev eth0*10:06:27* ++
awk '{split($4,a,"."); print a[1] "." a[2] "." a[3] "."
a[4]}'*10:06:27* ++ awk -F/ '{print $1}'*10:06:27* +
ADDR=192.168.201.4*10:06:27* + echo '192.168.201.4 engine'*10:06:27* +
pkgs_to_install=("ntp" "net-snmp" "ovirt-engine" "ovirt-log-collector"
"ovirt-engine-extension-aaa-ldap*" "otopi-debug-plugins"
"cronie")*10:06:27* + install_firewalld*10:06:27* + [[ el7 == \e\l\7
]]*10:06:27* + rpm -q firewalld*10:06:27* + systemctl enable
firewalld*10:06:27* + systemctl start firewalld*10:06:27* + [[ el7 ==
\e\l\7 ]]*10:06:27* + install_cmd='yum install --nogpgcheck
--downloaddir=/dev/shm -y'*10:06:27* + yum install --nogpgcheck
--downloaddir=/dev/shm -y ntp net-snmp ovirt-engine
ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*'
otopi-debug-plugins cronie*10:06:27* Error: Package:
ovirt-engine-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rubygem-fluent-plugin-viaq_data_model*10:06:27* Error: Package:
ovirt-engine-setup-plugin-ovirt-engine-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rh-postgresql95-postgresql-contrib*10:06:27* Error: Package:
ovirt-engine-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rubygem-fluent-plugin-rewrite-tag-filter*10:06:27* Error: Package:
ovirt-engine-setup-plugin-ovirt-engine-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rh-postgresql95-postgresql-server*10:06:27* Error: Package:
ovirt-engine-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rubygem-fluent-plugin-secure-forward*10:06:27* Error: Package:
ovirt-engine-tools-backup-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rh-postgresql95-postgresql*10:06:27* Error: Package:
ovirt-engine-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rh-postgresql95-postgresql-server*10:06:27* Error: Package:
1:java-1.8.0-openjdk-1.8.0.201.b09-2.el7_6.x86_64
(alocalsync)*10:06:27* Requires: gtk2(x86-64)*10:06:27*
Error: Package:
ovirt-engine-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rh-postgresql95-postgresql-contrib*10:06:27* Error: Package:
ovirt-engine-4.3.0-0.2.master.20190303132316.git026851f.el7.noarch
(alocalsync)*10:06:27* Requires:
rubygem-fluent-plugin-collectd-nest*10:06:27* + ret=1*10:06:27* + echo
'install failed with status 1'*10:06:27* + exit 1*10:06:27* *10:06:27*
* [Thread-4] Deploy VM lago-basic-suite-master-engine: ERROR (in
0:00:19)*10:07:41* * [Thread-2] Deploy VM
lago-basic-suite-master-host-0: ERROR (in 0:01:34)*10:07:41* #
Deploy environment: ERROR (in 0:01:34)*10:07:41* @ Deploy oVirt
environment: ERROR (in 0:01:34)*10:07:41* Error occured,
aborting*10:07:41* Traceback (most recent call last):*10:07:41* File
"/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in
do_run*10:07:41*
self.cli_plugins[args.ovirtverb].do_run(args)*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in
do_run*10:07:41* self._do_run(**vars(args))*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/utils.py", line 549, in
wrapper*10:07:41* return func(*args, **kwargs)*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/utils.py", line 560, in
wrapper*10:07:41* return func(*args, prefix=prefix,
**kwargs)*10:07:41* File
"/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 181, in
do_deploy*10:07:41* prefix.deploy()*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, in
wrapper*10:07:41* return func(*args, **kwargs)*10:07:41* File
"/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line 127,
in wrapper*10:07:41* return func(*args, **kwargs)*10:07:41* File
"/usr/lib/python2.7/site-packages/ovirtlago/prefix.py", line 284, in
deploy*10:07:41* return super(OvirtPrefix,
self).deploy()*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/sdk_utils.py", line 50, in
wrapped*10:07:41* return func(*args, **kwargs)*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, in
wrapper*10:07:41* return func(*args, **kwargs)*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/prefix.py", line 1671, in
deploy*10:07:41* self.virt_env.get_vms().values()*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/utils.py", line 103, in
invoke_in_parallel*10:07:41* return vt.join_all()*10:07:41* File
"/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
_ret_via_queue*10:07:41* queue.put({'return': func()})*10:07:41*
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1662, in
_deploy_host*10:07:41* host.name(),*10:07:41* LagoDeployError:
/dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-system-tests_manual_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_engine.sh
failed with status 1 on lago-basic-suite-master-engine
6 years
oVirt documentation vs. feature pages
by Greg Sheremeta
Hi,
TL;DR: please don't direct users to feature pages -- direct them to
end-user documentation instead. And maintain content separation between
end-user documentation and technical docs like feature pages.
...
Lately we've cleaned up documentation on ovirt.org, and I wanted to share
some of my thoughts about it. As a user experience focused person, I really
believe that clear and helpful documentation is crucial to the project's
success. I've also seen outdated documentation be a source of extreme
frustration for our users.
In the distant past, most of oVirt's documentation was written by
developers on a wiki, typically in the form of "feature pages." Feature
pages are basically technical design documents with occasionally some user
help sprinkled in.
With oVirt 4.0, we put a great set of clear documentation, written by
technical writers, on the oVirt website (which was also converted from a
wiki to a regular static site). This documentation is up to date with 4.2,
and we'll get the 4.3 content out there soon.
This official documentation lives at https://ovirt.org/documentation
and it should be considered the authoritative place for users to access our
documentation.
Feature pages, on the other hand, are (now) for developers. When you hear
the term "feature page", think "technical design document." Most users
should not be interested in this content.
It helps to think about the personas.
1. oVirt admins -- the person who sets up oVirt on Day 1 and 2. This is the
person who cares about and will read the Installation Guide and the
Administration Guide. These live under /documentation, e.g.
https://ovirt.org/documentation/install-guide/Installation_Guide.html
2. oVirt users -- the people who use oVirt to create, manage, and use
virtual machines, etc. This person will care about and read the VM Portal
Guide, User Guides, and such. These also live under /documentation, e.g.
https://ovirt.org/documentation/vmm-guide/Virtual_Machine_Management_Guid...
3. Developers -- you and I, and occasionally highly curious and technical
admins. These people might care about how the project works under the hood
-- high level designs, code flows, etc. Persona 2, oVirt users, do not care
about these details when they are learning to use oVirt, so end-user
documentation should not be polluted with this type of content. This
content now lives exclusively under /develop, the developer's section of
the site.
https://ovirt.org/develop/release-management/features/
Let's help our users by directing them to the end-user documentation, not
to feature pages. If you would like to contribute end-user documentation,
it should go under /documentation and not in a feature page. If you build a
new feature, the technical stuff goes under
/develop/release-management/features/ and the end-user stuff goes under
/documentation.
Feedback welcome :)
Best wishes,
Greg
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>
6 years
Updating Fedora 28 fail with "Package glusterfs-5.4-1.fc28.x86_64.rpm is not signed"
by Nir Soffer
# dnf update
...
Package glusterfs-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-libs-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-server-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-fuse-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-devel-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-api-devel-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-api-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-cli-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-client-xlators-5.4-1.fc28.x86_64.rpm is not signed
Package glusterfs-extra-xlators-5.4-1.fc28.x86_64.rpm is not signed
Package python3-gluster-5.4-1.fc28.x86_64.rpm is not signed
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED
This is a development laptop and I never installed or need glusterfs-server.
I could remove glusterfs-server, but other glusterfs packages seems to be
required by libvirt, libguestfs and qemu.
I tried "dnf clean all" and removed yum/dnf caches, but it does not help.
In the meantime I could update by excluding glusterfs. I hope someone has a
better
solution.
Nir
6 years, 1 month
Re: [JIRA] (OVIRT-2566) make network suite blocking
by Nir Soffer
On Mon, Nov 5, 2018 at 8:59 AM danken (oVirt JIRA) <
jira(a)ovirt-jira.atlassian.net> wrote:
> danken created OVIRT-2566:
> -----------------------------
>
> Summary: make network suite blocking
> Key: OVIRT-2566
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: OST
> Reporter: danken
> Assignee: infra
> Priority: High
>
>
> The network suite is executing nightly for almost a year. It has a caring
> team that tends to it, and it does not have false positives.
> Currently, it currently fails for a week on the 4.2 branch, but it is due
> to a production code bug.
>
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te...
>
> I would like to see this suite escalated to the importance of the basic
> suite, making it a gating condition for marking a collection of packages as
> "tested".
>
I'm ok with this only if it will gate *only* vdsm-network package, and it
will run in parallel, so
it does not slow down OST run.
For basic suite, we have too many random failures, so I don't think it is
useful, and we should
make it optional.
Nir
>
> [~gbenhaim(a)redhat.com], what should be done to make this happen?
>
>
>
>
> --
> This message was sent by Atlassian Jira
> (v1001.0.0-SNAPSHOT#100095)
> _______________________________________________
> Infra mailing list -- infra(a)ovirt.org
> To unsubscribe send an email to infra-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/VFQ776FLS2Q...
>
6 years, 1 month
