Dear Joe,
Thank you for your comment. Let us change these two objects to read-write
in the next version.
Thank you.
Hirochika
On Oct 9, 2013, at 3:10 AM, Joe Marcus Clarke jcla...@cisco.com wrote:
On 10/8/13 8:07 AM, Hirochika Asai wrote:
Hi,
I'm working on revising our draft and
-828-1401
-Original Message-
From: opsawg-boun...@ietf.org [mailto:opsawg-boun...@ietf.org] On
Behalf Of Hirochika Asai
Sent: Thursday, August 29, 2013 4:28 AM
To: Joe Marcus Clarke
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on
draft-asai-vmm
Punting the configuration problem to Netconf doesn't reduce the
modeling (or operational) complexity presented by read-write objects
like these. If you argue instead that they should be read-only, that's
another matter (though still fraught with complexity, given the ways
Netconf can work)
On 8/29/13 3:45 PM, Randy Presuhn wrote:
Hi -
From: Joe Marcus Clarke jcla...@cisco.com
To: Randy Presuhn randy_pres...@mindspring.com
Cc: opsawg@ietf.org
Sent: Thursday, August 29, 2013 12:29 PM
Subject: Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on
draft-asai-vmm-mib-04
Hi -
From: Joe Marcus Clarke jcla...@cisco.com
To: Randy Presuhn randy_pres...@mindspring.com
Cc: opsawg@ietf.org
Sent: Thursday, August 29, 2013 4:11 PM
Subject: Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on
draft-asai-vmm-mib-04)
...
I would be happy with read-only objects
Thank you for your comments and I'm sorry for responding late.
On Aug 20, 2013, at 3:37 PM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
Is there a strong push from operators to toggle these values via SNMP?
Remeber that this is a MAX-ACCESS. RFC 2578 section 7.3 says
On 8/24/13 5:27 AM, Hirochika Asai wrote:
Thank you for your comments and I'm sorry for responding late.
On Aug 20, 2013, at 3:37 PM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
Is there a strong push from operators to toggle these values via SNMP?
Remeber that
Hi -
From: Joe Marcus Clarke jcla...@cisco.com
Sent: Aug 23, 2013 11:56 AM
To: Michael MacFaden m...@vmware.com, opsawg@ietf.org
Subject: Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on
draft-asai-vmm-mib-04)
...
My other comment (not quoted here) is that I was asking if some more
On 8/23/13 3:41 PM, Randy Presuhn wrote:
Hi -
From: Joe Marcus Clarke jcla...@cisco.com
Sent: Aug 23, 2013 11:56 AM
To: Michael MacFaden m...@vmware.com, opsawg@ietf.org
Subject: Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on
draft-asai-vmm-mib-04)
...
My other comment
On 8/23/13 5:01 PM, Michael MacFaden wrote:
Hi Joe,
Think there is agreement on the list that changes to the objects reported in
VMM-MIB are not
coming in through SNMP.
If VMM-MIB has managed objects whose value are configured
via other means *and* the hypervisor in question
On Wed, Aug 21, 2013 at 02:27:08PM -0400, Joe Marcus Clarke wrote:
That's fair. I was not aware of the ability to adjust VM CPU and memory
on the fly without touching the config. That said, I struggle to
understand the use case of doing this via SNMP versus a more reliable API.
In the MIB
On 8/20/13 2:37 AM, Juergen Schoenwaelder wrote:
On Mon, Aug 19, 2013 at 04:38:28PM -0400, Joe Marcus Clarke wrote:
We seem to agree on the general scope. Now we have to determine which
objects reasonably have a MAX-ACCESS or read-write. For me, it seems
that vmAutoStart likely should indeed
On Mon, Aug 19, 2013 at 04:38:28PM -0400, Joe Marcus Clarke wrote:
We seem to agree on the general scope. Now we have to determine which
objects reasonably have a MAX-ACCESS or read-write. For me, it seems
that vmAutoStart likely should indeed be read-only. However, as far as
I know,
Marking this proposal as Joe-3
JMC: The purpose of this MIB is not to provide configuration of the
hypervisor. Quoting section 3.2:
The MIB module provides a few writable objects that can be used to
make non-persistent changes, e.g., changing the memory allocation or
the CPU
On Mon, Aug 19, 2013 at 11:26:06AM -0700, Michael MacFaden wrote:
Marking this proposal as Joe-3
JMC: The purpose of this MIB is not to provide configuration of the
hypervisor. Quoting section 3.2:
The MIB module provides a few writable objects that can be used to
make
On 8/19/13 2:26 PM, Michael MacFaden wrote:
Marking this proposal as Joe-3
JMC: The purpose of this MIB is not to provide configuration of the
hypervisor. Quoting section 3.2:
The MIB module provides a few writable objects that can be used to
make non-persistent changes, e.g.,
On 8/19/13 2:34 PM, Juergen Schoenwaelder wrote:
On Mon, Aug 19, 2013 at 11:26:06AM -0700, Michael MacFaden wrote:
Marking this proposal as Joe-3
JMC: The purpose of this MIB is not to provide configuration of the
hypervisor. Quoting section 3.2:
The MIB module provides a few writable
17 matches
Mail list logo
