tacker

vim-register fails in mitaka version, complains that 'Vim' not defined

Asked by Rathnakumar Kayyar

I did a manual installation of OoenStack mitaka on CentOs, followed by tacker (mitaka). Followed the documentation, and generally could get it working without problems. (Had couple of minor issues which probably need more documentation - had to specify bind_port 9890 in tacker.conf, had to force install requirements, pathname changes specific to CentOs etc.)

When I try vim-register, I get an error - summary is:
2016-09-01 12:27:09.741 5294 TRACE tacker.api.v1.resource InvalidRequestError: O
ne or more mappers failed to initialize - can't proceed with initialization of o
ther mappers. Original exception was: When initializinnfvog mapper Mapper|Device|de
vices, expression 'Vim' failed to locate a name ("name 'Vim' is not defined"). I
f this is a class name, consider adding this relationship() to the <class 'tacke
r.db.vm.vm_db.Device'> class after both dependent classes have been defined.

I saw that Vim is defined in db.nfvo.nfvo_db, tried to import it in vm.vm_db.py but saw that it leads to circular importing. Fails saying that 'vnfm' not found.
If I comment out the following line, I am able to complete vim-register:
line 125 in vm_db.py: vim = orm.relationship('Vim') (class Device definition).

Looks like this is due to something I did/didn't do. Any clues?

RK

Question information

Language:
English Edit question
Status:
Expired
For:
tacker Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
venkatamahesh (venkatamaheshkotha) said : 		#1

Hi,

Can you please submit your log file.
And also please follow these changes : https://review.openstack.org/#/c/353258/. I have submitted after successful installation.
-
Mahesh

Revision history for this message
Rathnakumar Kayyar (rkayyar) said : 		#2

Mahesh, I did the configuration delta changes as per the updated document. However, couldn't start the server with commonservices plugin. I have attached two log files - one with commonservices in tacker.conf.
Second one is the complete logs for the original problem I reported yesterday ('Vim' not defined).

1. Commonservices plugin fails (note: I am using the stable mitaka version of tacker, not the latest):
http://pastebin.com/Uf5ATBYG

2. Full log for 'Vim' undefined error
http://pastebin.com/YzmmVR5A

Thanks for the support.
rk

Revision history for this message
Sridhar Ramaswamy (srics-r) said : 		#3

Remove commonservices in the services_plugin as it is applicable only for master (newton) .

Revision history for this message
venkatamahesh (venkatamaheshkotha) said : 		#4

Hi Rathnakumar,

Are you getting the error again. ?

Revision history for this message
Rathnakumar Kayyar (rkayyar) said : 		#5

Mahesh,
Yes, actually I didn't make further progress. I had already tried Sridhar's input (removing services_plugin), and the logs I pasted above (2nd pastebin link) was after that.

If there are other clues, I will be happy to try. Moving to Newton is not an option for now. But we will need VNFM-EMS interfaces and virtual resource usage information and other ETSI MANO-promised goodies , so was planning to come back and check the Tacker roadmap again.
rk

Revision history for this message
Launchpad Janitor (janitor) said : 		#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.