Trouble with the "Domains" tab

[Andrew P]

Hey guys,

I'm trying to set up a fresh install of openIPAM, and it seems that
when I try to create a domain from the domains tab, I get a 404. The
other tabs seem to work normally.

I've checked the source tree, and there's a domains.py, but there's no
domains.pyc.

I am using the integrated web server right now.

Thanks in advance for any assistance!

-Andrew.

--
You received this message because you are subscribed to the Google Groups "openIPAM" group.
To post to this group, send email to open...@googlegroups.com.
To unsubscribe from this group, send email to openipam+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openipam?hl=en.

[Eldon Koyle]

I don't think that page was ever implemented. We don't have many people
who are allowed to create groups, and the CLI tool has always fulfilled
our needs.

To start the CLI, I usually run:
PYTHONPATH=~/src/trunk/openIPAM ~/src/trunk/openIPAM/scripts/ipm.py https://ipam.backend:8443/api/

(adjust the URL to match your backend config, the trailing / is
required)

Then:

openipam % add_domain
slave domain [y/N]: n
name []: some.domain.com
description []: this is an example domain

*********
Please check your values:
name: some.domain.com
description: this is an example domain
verify change [y/N]: y


--
Eldon Koyle
System Administration Operations
Information Technology
Utah State University
--
We must believe that it is the darkest before the dawn of a beautiful
new world. We will see it when we believe it.
-- Saul Alinsky

[Eldon Koyle]

On May 18 16:11-0600, Eldon Koyle wrote:
> I don't think that page was ever implemented. We don't have many people
> who are allowed to create groups, and the CLI tool has always fulfilled

I meant domains, not groups (although both are true). If you have any
questions on the CLI tool, please feel free to ask. I need to do better
at documentation.

--
Eldon Koyle
System Administration Operations
Information Technology
Utah State University
--

If your hands are clean and your cause is just and your demands are
reasonable, at least it's a start.

[Andrew Preece]

the CLI is not working out so well for me here, either:

I'm not sure why it's got an issue with a 302 redirect?

#PYTHONPATH=/usr/local/openipam/openIPAM/ /usr/local/openipam/openIPAM/scripts/ipm.py https://localhost:8443/api/Connecting to url https://localhost:8443/api/

Username: admin
Password:

Traceback (most recent call last):
File "/usr/local/openipam/openIPAM/scripts/ipm.py", line 953, in <module>
cli = IPMCmdInterface( iface )
File "/usr/local/openipam/openIPAM/scripts/ipm.py", line 121, in __init__
for i in self.iface.get_dns_types():
File "/usr/local/openipam/openIPAM/scripts/ipm.py", line 54, in make_call
self.ipam.login( self.__user, self.__pass )
File "/usr/lib/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/local/openipam/openIPAM/openipam/web/resource/xmlrpcclient.py", line 130, in request
headers
xmlrpclib.ProtocolError: <ProtocolError for localhost:8443/api/: 302 Found>

[Eldon Koyle]

Hmm... I wonder if we introduced a bug in the standalone code.

Just to verify, the URL should match the xmlrpc_* settings in
openipam_config/frontend.py (ie. http://xmlrpc_host:xmlrpc_port/api/ or
https:// if xmlrpc_ssl_enabled=True).

Can you tell where it is redirecting to? The CLI code probably won't
handle a redirect.

We haven't used the standalone server since we started using openipam in
production. It has some SSL issues that cause it to stop handling
requests periodically.

--
Eldon Koyle
System Administration Operations
Information Technology
Utah State University
--

All people are born alike -- except Republicans and Democrats.
-- Groucho Marx