Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."
Today's Topics:
1. Re: [Netdot-users] Seeking feedback about DBMS support
(Schroeder, AJ (GE Healthcare, consultant))
2. Re: [Netdot-users] Seeking feedback about DBMS support
(Carlos Vicente)
3. [SCM] UNNAMED PROJECT branch netdot-1.0 updated.
netdot-1.0.1-58-g1f466f6 ([email protected])
4. [Netdot - Feature #1692] (New) Many-to-many relationship
between assets and devices ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 27 Sep 2012 14:55:55 +0000
From: "Schroeder, AJ (GE Healthcare, consultant)"
<[email protected]>
Subject: Re: [Netdot-devel] [Netdot-users] Seeking feedback about DBMS
support
To: Carlos Vicente <[email protected]>, netdot-users
<[email protected]>, netdot-devel
<[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
I am not a DBA by trade, so I can't really speak to the technical aspects of
each respective database engines. I have used Pg and MySQL backends with
various software packages.
I have done a little development in the past and I used Pg and really liked it,
it seemed to be a more feature rich and mature platform than MySQL. Of course
this was all about 7 years ago so I am sure that MySQL has gotten better.
So for me, based on past experience I am giving a thumbs up to Pg.
AJ
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Carlos Vicente
Sent: Monday, September 24, 2012 3:10 PM
To: netdot-users; netdot-devel
Subject: [Netdot-users] Seeking feedback about DBMS support
Dear Netdot community,
One of our initial design goals for Netdot was to make it DB-agnostic.
We aimed at supporting both MySQL and Postgres equally. However, our production
systems at the University of Oregon have always been based on MySQL, so Pg
support was somewhat lagging. It still is.
The sad truth is that it takes considerable time and effort to support two
backends.
At a recent discussion we talked about the possibility of supporting only
PostgreSQL in the future. There are a few things that make Pg
attractive: native support for IPv4 and IPv6 addresses, table partitions, etc.
Pg is also not owned by Oracle ;-)
A decision like this can't be made lightly. We certainly do not want to
alienate administrators out there.
My hunch is that most people don't care about the backend, and if they do, they
prefer Pg. Am I right?
What do you all think?
--
cv
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
------------------------------
Message: 2
Date: Thu, 27 Sep 2012 11:11:15 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-devel] [Netdot-users] Seeking feedback about DBMS
support
To: netdot-users <[email protected]>, netdot-devel
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Dear all,
Thank you very much for your feedback. Between this mailing list and FB,
so far we received 11 replies. Only one person had a preference for
MySQL over Pg.
We will keep you informed about our future plans.
Regards,
--
cv
------------------------------
Message: 3
Date: Thu, 27 Sep 2012 08:20:03 -0700
From: [email protected]
Subject: [Netdot-devel] [SCM] UNNAMED PROJECT branch netdot-1.0
updated. netdot-1.0.1-58-g1f466f6
To: [email protected]
Message-ID: <[email protected]>
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "UNNAMED PROJECT".
The branch, netdot-1.0 has been updated
via 1f466f61c084bf75260166e4bd304eff9dfdcc86 (commit)
from 6489894af3d875a03448a9c67348395cab635c33 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 1f466f61c084bf75260166e4bd304eff9dfdcc86
Author: Carlos Vicente <[email protected]>
Date: Thu Sep 27 11:19:59 2012 -0400
Fixes related to Foundry CLI interface
diff --git a/etc/Default.conf b/etc/Default.conf
index 83238c5..9dd32d7 100644
--- a/etc/Default.conf
+++ b/etc/Default.conf
@@ -459,7 +459,12 @@ FETCH_DEVICE_INFO_VIA_CLI => {
'^cisco76\d{2}' => 'CiscoIOS',
'^catalyst2960' => 'CiscoCat',
'^cat(:?alist)?3560' => 'CiscoCat',
- '^sqnNetIronMLX\d{1,2}' => 'FoundryIW',
+ '^snNetIronMLX\d{1,2}' => 'FoundryIW',
+ '^snFGS648P' => 'FoundryIW',
+ '^snFLS648' => 'FoundryIW',
+ '^snFWS648G' => 'FoundryIW',
+ '^snTI2X24' => 'FoundryIW',
+ '^snFastIronStackICX' => 'FoundryIW',
},
# Device CLI credentials. These are used for fetching
diff --git a/lib/Netdot/Model/Device/CLI/FoundryIW.pm
b/lib/Netdot/Model/Device/CLI/FoundryIW.pm
index 7ca88e6..4431cd7 100644
--- a/lib/Netdot/Model/Device/CLI/FoundryIW.pm
+++ b/lib/Netdot/Model/Device/CLI/FoundryIW.pm
@@ -328,6 +328,8 @@ sub _reduce_iname{
my ($self, $name) = @_;
return unless $name;
$name =~ s/^.*Ethernet//;
+ $name =~ s/-.*$//; # Fix LACPa
+ $name =~ s/\*.*$//; # Fix LACP
return $name;
}
-----------------------------------------------------------------------
Summary of changes:
etc/Default.conf | 7 ++++++-
lib/Netdot/Model/Device/CLI/FoundryIW.pm | 2 ++
2 files changed, 8 insertions(+), 1 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT
------------------------------
Message: 4
Date: Thu, 27 Sep 2012 10:52:26 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1692] (New) Many-to-many
relationship between assets and devices
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1692 has been reported by Carlos Vicente.
----------------------------------------
Feature #1692: Many-to-many relationship between assets and devices
https://osl.uoregon.edu/redmine/issues/1692
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee: Carlos Vicente
Category: DeviceManagement
Target version:
Resolution:
As it is today, an asset can have many devices. This makes sense with
virtualized devices (think Nexus). The other case, which is not supported, is a
single device composed of many assets (switch stacks).
Netdot could determine this by looking for modules of class "stack" in the
Entity MIB.
We will need a join table.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 66, Issue 24
********************************************
