Hello all,
My name is Mor, I am from the RHV networking team.
I am experiencing an issue with PCI device slot ID's and network interface
names that appear sometimes on my environment. I was advised to contact
this mailing-list in hope to get explanation or possible solution for this
issue.
The i
Hello all,
My name is Mor, I am from the RHV networking team.
I am experiencing an issue with PCI device slot ID's and network interface
names that appear sometimes on my environment. I was advised to contact
this mailing-list in hope to get explanation or possible solution for this
issue.
The i
On Wed, Oct 25, 2017 at 9:33 AM Sandro Bonazzola
wrote:
> 2017-10-20 20:05 GMT+02:00 Yaniv Kaul :
>
>>
>>
>> On Fri, Oct 20, 2017 at 7:56 PM, Nir Soffer wrote:
>>
>>> On Fri, Oct 20, 2017 at 11:37 AM Sandro Bonazzola
>>> wrote:
>>>
Just an heads up we have improvement margin on vdsm spec f
On Wed, Oct 25, 2017 at 3:21 PM, Nir Soffer wrote:
> On Wed, Oct 25, 2017 at 9:33 AM Sandro Bonazzola
> wrote:
>
>> 2017-10-20 20:05 GMT+02:00 Yaniv Kaul :
>>
>>>
>>>
>>> On Fri, Oct 20, 2017 at 7:56 PM, Nir Soffer wrote:
>>>
On Fri, Oct 20, 2017 at 11:37 AM Sandro Bonazzola
wrote:
>
Hello oVirt developers.
Here is our question #3.
*File: *AppErrors
*Resource ID: *VAR__ACTION__TRANSFER
*String: *$action transfer
*Question:* When this is used in "Cannot ${action} ${type}. ", what "type"
this action is combined with? (i.e. what is transferred?)
Thank you,
Yuko
Re-posting.
Could anyone help us with this?
On Mon, Oct 23, 2017 at 9:31 AM, Yuko Katabami wrote:
> Hello oVirt developers.
> I have started translating Admin Portal strings for 4.2 from today and
> here is my first question.
>
>
> *File: *AppErrors
> *Resource ID: *ACTION_TYPE_FAILED_AFFINITY_H
Phillip might know
On Wed, Oct 25, 2017 at 11:25 AM, Yuko Katabami wrote:
> Re-posting.
> Could anyone help us with this?
>
> On Mon, Oct 23, 2017 at 9:31 AM, Yuko Katabami
> wrote:
>
>> Hello oVirt developers.
>> I have started translating Admin Portal strings for 4.2 from today and
>> here is
Hi,
the affinity groups allow defining VM to host affinity rules. This
error is shown when the same pair of host and VM has both positive and
negative affinity rule defined. Both host and VM are specified by the
user, but not necessarily directly as there can be a conflict chain
like this: A + B,
Thank you Greg and Martin.
That makes a clear sense.
I will apply this interpretation to my translation.
Kind regards,
Yuko
On Thu, Oct 26, 2017 at 5:04 AM, Martin Sivak wrote:
> Hi,
>
> the affinity groups allow defining VM to host affinity rules. This
> error is shown when the same pair of h
Hello again.
Here is my next question.
*File: *AppErrors
*Resource ID: *VAR__TYPE__LUNS
*String: *@type LUNs
*Question:* Is this a typo for "$type LUNs"?
Yuko
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Hello oVirt developers.
I have another question.
*File: *AppErrors
*Resource ID: *VM_SLA_POLICY_UNCHANGED
*String: *VM SLA Policy command does not change anything.
*Question:* Could someone explain to me what this actually means? Does it
mean "the operation (user performed) to update VM's SLA
Hi Yuko,
The answer is "Virtual Disk".
Regards,
Idan
On Wed, Oct 25, 2017 at 6:22 PM, Yuko Katabami wrote:
> Hello oVirt developers.
> Here is our question #3.
>
> *File: *AppErrors
>
> *Resource ID: *VAR__ACTION__TRANSFER
>
> *String: *$action transfer
> *Question:* When this is used
Hi Yuko,
I am not sure where exactly you meant that the typo is.
- "LUNs" (in "@type LUNs") seems ok since LUN is an acronym and the "s" is
for the plural.
- "LUNS" (in "VAR__TYPE__LUNS") seems ok since variable names in AppErrors
should be in capital letters.
If I misunderstood please say so.
I'm looking at some supervdsm log, and I'm seeing these commands:
/usr/bin/taskset --cpu-list 0-55 /usr/libexec/vdsm/fc-scan
and:
/usr/bin/taskset --cpu-list 0-55 /usr/bin/mount -t nfs -o
soft,nosharecache,timeo=600,retrans=6 10.10.10.1:/NFS/images
And so on (also for iscsiadm).
Why do we need to
14 matches
Mail list logo
