Re: [openstack-dev] [magnum] [ocata] after installation, magnum is not found

2017-03-09 Thread Spyros Trigazis 
Hi,

You haven't installed the magnum client. The service is running
but you don't have the client.

You need the client installed and to create and source the RC file.

Spyros

On 9 March 2017 at 07:49, Yu Wei  wrote:

> Hi guys,
>
> After installing openstack ocata magnum, magnum is not found.
>
> However, magnum-api and magnum-conduct are running well.
>
> How could I fix such problem? Is this bug in ocata?
>
>
> [root@controller bin]# systemctl status openstack-magnum-api.service
> openstack-magnum-conductor.service
> ● openstack-magnum-api.service - OpenStack Magnum API Service
>Loaded: loaded (/usr/lib/systemd/system/openstack-magnum-api.service;
> enabled; vendor preset: disabled)
>Active: active (running) since Thu 2017-03-09 11:51:33 CST; 13min ago
>  Main PID: 16195 (magnum-api)
>CGroup: /system.slice/openstack-magnum-api.service
>└─16195 /usr/bin/python2 /usr/bin/magnum-api
>
> Mar 09 11:51:33 controller systemd[1]: Started OpenStack Magnum API
> Service.
> Mar 09 11:51:33 controller systemd[1]: Starting OpenStack Magnum API
> Service...
> Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.646
> 16195 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now
> registers SIGUSR1 and SIGUSR2 by default for...rate reports.
> Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.647
> 16195 INFO magnum.api.app [-] Full WSGI config used:
> /etc/magnum/api-paste.ini
> Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.751
> 16195 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set
> with keystone_authtoken.service_token_role...this to True.
> Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.762
> 16195 INFO magnum.cmd.api [-] Starting server in PID 16195
> Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.767
> 16195 INFO magnum.cmd.api [-] Serving on http://192.168.111.20:9511
> Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.767
> 16195 INFO magnum.cmd.api [-] Server will handle each request in a new
> process up to 2 concurrent processes
> Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.768
> 16195 INFO werkzeug [-]  * Running on http://192.168.111.20:9511/
>
> ● openstack-magnum-conductor.service - Openstack Magnum Conductor Service
>Loaded: loaded (/usr/lib/systemd/system/openstack-magnum-conductor.service;
> enabled; vendor preset: disabled)
>Active: active (running) since Thu 2017-03-09 11:51:33 CST; 13min ago
>  Main PID: 16200 (magnum-conducto)
>CGroup: /system.slice/openstack-magnum-conductor.service
>└─16200 /usr/bin/python2 /usr/bin/magnum-conductor
>
> Mar 09 11:51:33 controller systemd[1]: Started Openstack Magnum Conductor
> Service.
> Mar 09 11:51:33 controller systemd[1]: Starting Openstack Magnum Conductor
> Service...
> Mar 09 11:51:34 controller magnum-conductor[16200]: 2017-03-09
> 11:51:34.640 16200 WARNING oslo_reports.guru_meditation_report [-] Guru
> meditation now registers SIGUSR1 and SIGUSR2 by defau...rate reports.
> Mar 09 11:51:34 controller magnum-conductor[16200]: 2017-03-09
> 11:51:34.640 16200 INFO magnum.cmd.conductor [-] Starting server in PID
> 16200
> Mar 09 11:51:34 controller magnum-conductor[16200]:
> /usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py:200:
> FutureWarning: The access_policy argument is changing its default value to
>  Mar 09 11:51:34 controller magnum-conductor[16200]: access_policy)
> Mar 09 11:51:34 controller magnum-conductor[16200]: 2017-03-09
> 11:51:34.648 16200 INFO oslo_messaging.server [-] blocking executor handles
> only one message at once. threading or eventlet e... recommended.
> Hint: Some lines were ellipsized, use -l to show in full.
> [root@controller bin]# magnum service-list
> bash: magnum: command not found...
>
>
> Thanks,
>
> Jared, (韦煜）
> Software developer
> Interested in open source software, big data, Linux
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [magnum] [ocata] after installation, magnum is not found

2017-03-08 Thread Yu Wei 
Hi guys,

After installing openstack ocata magnum, magnum is not found.

However, magnum-api and magnum-conduct are running well.

How could I fix such problem? Is this bug in ocata?


[root@controller bin]# systemctl status openstack-magnum-api.service   
openstack-magnum-conductor.service
● openstack-magnum-api.service - OpenStack Magnum API Service
   Loaded: loaded (/usr/lib/systemd/system/openstack-magnum-api.service; 
enabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-03-09 11:51:33 CST; 13min ago
 Main PID: 16195 (magnum-api)
   CGroup: /system.slice/openstack-magnum-api.service
   └─16195 /usr/bin/python2 /usr/bin/magnum-api

Mar 09 11:51:33 controller systemd[1]: Started OpenStack Magnum API Service.
Mar 09 11:51:33 controller systemd[1]: Starting OpenStack Magnum API Service...
Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.646 16195 
WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers 
SIGUSR1 and SIGUSR2 by default for...rate reports.
Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.647 16195 
INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini
Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.751 16195 
WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with 
keystone_authtoken.service_token_role...this to True.
Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.762 16195 
INFO magnum.cmd.api [-] Starting server in PID 16195
Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.767 16195 
INFO magnum.cmd.api [-] Serving on http://192.168.111.20:9511
Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.767 16195 
INFO magnum.cmd.api [-] Server will handle each request in a new process up to 
2 concurrent processes
Mar 09 11:51:34 controller magnum-api[16195]: 2017-03-09 11:51:34.768 16195 
INFO werkzeug [-]  * Running on http://192.168.111.20:9511/

● openstack-magnum-conductor.service - Openstack Magnum Conductor Service
   Loaded: loaded (/usr/lib/systemd/system/openstack-magnum-conductor.service; 
enabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-03-09 11:51:33 CST; 13min ago
 Main PID: 16200 (magnum-conducto)
   CGroup: /system.slice/openstack-magnum-conductor.service
   └─16200 /usr/bin/python2 /usr/bin/magnum-conductor

Mar 09 11:51:33 controller systemd[1]: Started Openstack Magnum Conductor 
Service.
Mar 09 11:51:33 controller systemd[1]: Starting Openstack Magnum Conductor 
Service...
Mar 09 11:51:34 controller magnum-conductor[16200]: 2017-03-09 11:51:34.640 
16200 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now 
registers SIGUSR1 and SIGUSR2 by defau...rate reports.
Mar 09 11:51:34 controller magnum-conductor[16200]: 2017-03-09 11:51:34.640 
16200 INFO magnum.cmd.conductor [-] Starting server in PID 16200
Mar 09 11:51:34 controller magnum-conductor[16200]: 
/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py:200: 
FutureWarning: The access_policy argument is changing its default value to 
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev