Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
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-users digest..."
Today's Topics:
1. Re: Request for testing a script to migrate netdot
installations from MySQL to PostgreSQL (Anton Berezin)
2. possible 1.0.5 RC1 issues to look into (D. Bischof)
3. Re: Request for testing a script to migrate netdot
installations from MySQL to PostgreSQL (Vincent Magnin)
----------------------------------------------------------------------
Message: 1
Date: Mon, 20 Jan 2014 22:06:18 +0100
From: Anton Berezin <[email protected]>
Subject: Re: [Netdot-users] Request for testing a script to migrate
netdot installations from MySQL to PostgreSQL
To: Vincent Magnin <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Vincent,
Bringing the discussion back to the list.
On Fri, Jan 17, 2014 at 01:16:52PM +0100, Anton Berezin wrote:
> On Fri, Jan 17, 2014 at 11:08:07AM +0000, Vincent Magnin wrote:
> Are you seeing a particular error message from psql, or are you just getting
> corrupted data?
>
> What Pg version are you using? It might that what we are seeing is this
> (take from http://www.postgresql.org/docs/9.1/static/datatype-binary.html):
>
> The bytea type supports two external formats for input and output:
> PostgreSQL's historical "escape" format, and "hex" format. [...]
> Note that the hex format was introduced in PostgreSQL 9.0; earlier
> versions and some tools don't understand it.
>
> If this is the case, I'll have to redo the bytea support to use the
> historical escape format instead of the hex one - at least if the script
> detects older PostgreSQL versions...
This is now done, so the fresh version at
https://raw.github.com/tobez/Netdot/master/upgrade/migrate-mysql-pg
should handle binary data for older and newer versions of Pg alike.
\Anton.
--
Our society can survive even a large amount of irrational regulation.
-- John McCarthy
------------------------------
Message: 2
Date: Tue, 21 Jan 2014 10:51:24 +0100 (CET)
From: "D. Bischof" <[email protected]>
Subject: [Netdot-users] possible 1.0.5 RC1 issues to look into
To: [email protected]
Message-ID: <alpine.LSU.2.11.1401211016200.17007@fred>
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Hi,
I've successfully deployed Netdot 1.0.5 RC1 for my zone/subnet use case.
I'm (by far) not using all of Netdot's features, I just want to generate
ISC BIND zone files and a DHCP configuration file. Also, I want to grant
restricted access to colleagues.
Therefore I created a Contact List with several Persons of User Type
"User". The permissions are as follows:
---
User,Access Right
Doe J,Ipblock 141.nnn.nnn.0/24 - view
Doe J,Ipblock 141.nnn.nnn.0/24 - edit
Doe J,Ipblock 141.nnn.nnn.0/24 - delete
Doe J,Ipblock 141.nnn.nnn.0/24 - choose_ip
Doe J,Zone nnn.nnn.141.in-addr.arpa - view
Doe J,Zone some.where.de - view
Doe J,Zone some.where.de - edit
Doe J,Zone some.where.de - delete
Doe J,ContactList A-TEAM - view
---
It's working reliably and I'm basically happy.
However, I found the following possible issues, that may be worth to look
into:
- users can't create or edit "DHCP Host" Ethernet address entries for
existing IP records. They can, however, add Ethernet address entries when
adding a new host.
- when adding an Ethernet address as DHCP host entry, the IP address is
used for the "host" entry in dhcpd.conf. I expected the hostname to be
used for this.
- users with the above permissions are able to add entries to the reverse
zone (A records!). I guess that this is not the intended behaviour.
Mit freundlichen Gruessen/With best regards,
--Daniel.
------------------------------
Message: 3
Date: Tue, 21 Jan 2014 10:58:35 +0000
From: Vincent Magnin <[email protected]>
Subject: Re: [Netdot-users] Request for testing a script to migrate
netdot installations from MySQL to PostgreSQL
To: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
Hi Anton,
I was able to run netdot on a postgresql 8.4 database (RHEL6.4 Host)
using your script successfully:
- I had to correct some "corrupted" values on my Mysql DB (mostly NULL
constraint errors)
Now, I've some error related to postgres itself. I'll look after these
errors more carefully later:
> DBD::Pg::db selectrow_array failed: ERROR: relation "binfile" does not exist
> LINE 1: SELECT bindata FROM binfile WHERE id = 3
> ^ [for Statement "SELECT bindata FROM binfile WHERE id = 3"] at
> /usr/local/netdot/lib/Netdot/Model
> /Picture.pm line 90.
Regards,
Vincent
Anton Berezin <[email protected]> a ?crit?:
> Hi Vincent,
>
> Bringing the discussion back to the list.
>
> On Fri, Jan 17, 2014 at 01:16:52PM +0100, Anton Berezin wrote:
>> On Fri, Jan 17, 2014 at 11:08:07AM +0000, Vincent Magnin wrote:
>
>> Are you seeing a particular error message from psql, or are you just getting
>> corrupted data?
>>
>> What Pg version are you using? It might that what we are seeing is this
>> (take from http://www.postgresql.org/docs/9.1/static/datatype-binary.html):
>>
>> The bytea type supports two external formats for input and output:
>> PostgreSQL's historical "escape" format, and "hex" format. [...]
>> Note that the hex format was introduced in PostgreSQL 9.0; earlier
>> versions and some tools don't understand it.
>>
>> If this is the case, I'll have to redo the bytea support to use the
>> historical escape format instead of the hex one - at least if the script
>> detects older PostgreSQL versions...
>
> This is now done, so the fresh version at
> https://raw.github.com/tobez/Netdot/master/upgrade/migrate-mysql-pg
> should handle binary data for older and newer versions of Pg alike.
>
> \Anton.
> --
> Our society can survive even a large amount of irrational regulation.
> -- John McCarthy
--
------------------------------------------------------------------------
Vincent Magnin [email protected]
Ing?nieur R?seau & T?l?com +41 21 692 22 48
UNIL, Centre Informatique, 1015 Lausanne
Switzerland
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 62, Issue 7
*******************************************
