Re: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"!

[Tobias Urdin]

Yeah, that's it :)

Can post the apache2 config here, this is the one we use which is generated by 
puppet, you'll need the mod_wsgi module as well.


  ServerName hostnamehere

  ## Vhost docroot
  DocumentRoot "/usr/lib/cgi-bin/gnocchi"

  ## Directories, there should at least be a declaration for 
/usr/lib/cgi-bin/gnocchi

  
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Require all granted
  

  ## Logging
  ErrorLog "/var/log/apache2/gnocchi_wsgi_error.log"
  ServerSignature Off
  CustomLog "/var/log/apache2/gnocchi_wsgi_access.log" combined
  SetEnvIf X-Forwarded-Proto https HTTPS=1
  WSGIApplicationGroup %{GLOBAL}
  WSGIDaemonProcess gnocchi display-name=gnocchi_wsgi group=gnocchi processes=2 
threads=1 user=gnocchi
  WSGIProcessGroup gnocchi
  WSGIScriptAlias / "/usr/lib/cgi-bin/gnocchi/app"


On 06/07/2018 10:54 PM, Martinx - ジェームズ wrote:
Worth to mention that I still have to test python-gnocchi, my confs are wrong 
but, it is installed...   :-P

On Thu, 7 Jun 2018 at 15:57, Martinx - ジェームズ 
mailto:thiagocmarti...@gmail.com>> wrote:
Corey,

 I still don't get it... The package gnocchi-api is basically empty.

 It have only 1 single text file: 
"/etc/apache2/sites-available/gnocchi-api.conf"!

 The problem is that it depends on "python3-gnocchi" and 
"libapache2-mod-wsgi-py3", which brings the problem...

 So, the workaround looks quite simple!

 Instead of running "apt install gnocchi-api", I'm doing:

---
 apt install python-gnocchi # which brings Gnocchi API (/usr/bin/gnocchi-api) 
for Python 2, then:

 apt download gnocchi-api

 # Extract the "/etc/apache2/sites-available/gnocchi-api.conf" file out from 
"gnocchi-api_4.2.4-0ubuntu1_all.deb" and manually copy to 
/etc/apache/sites-available".
---



On 5 June 2018 at 10:30, Corey Bryant 
mailto:corey.bry...@canonical.com>> wrote:
Hi Martin,

Thanks for bringing this up. I replied in the bug, but pasting some of my 
response below:

gnocchi-api only supports py3 for now in bionic/queens and above.

Most OpenStack packages in Ubuntu have not yet received py3 support. That is a 
focus for the cosmic cycle. Where possible the plan is to install py2 by 
default and py3 as an alternative to prevent all-in-one issues like this.

In other words, 'sudo apt install python3-keystone keystone' would install 
python3 packages, and (assuming python3-keystone was not already installed) 
'sudo apt install keystone' would install python2 packages.

That's not the case for gnocchi-api, obviously, as it only installs py3 
packages which conflicts with other python packages if and only if you're 
installing on the same machine as other py2 services. Most modern production 
deployments isolate services in one way or another (e.g. containers such as LXD 
or docker) so there's a clear work around.

With that said, we can probably add py2 alternative packages to the Depends for 
gnocchi-api allowing py2 installs, however I seem to remember gnocchi-api was 
forced to move to py3 for a reason. I'm not remembering why though atm.

Thanks,

Corey

On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ 
mailto:thiagocmarti...@gmail.com>> wrote:
Thank you!

On 4 June 2018 at 21:25, pablo brunetti 
mailto:pablobrune...@hotmail.com>> wrote:

Hello,


This bug is confirmed in 
https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992

Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : Bugs : 
gnocchi package : 
Ubuntu
bugs.launchpad.net
Since the two wsgi modules are conflicting, installing gnocchi-api breaks other 
OpenStack services.



Pablo.




De: Martinx - ジェームズ 
mailto:thiagocmarti...@gmail.com>>
Enviado: segunda-feira, 4 de junho de 2018 21:53
Para: openstack@lists.openstack.org; 
James Page
Assunto: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries 
to remove both "keystone" and "openstack-dashboard"!

Hello,

 I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, the 
"gnocchi-api" package tries to uninstall Keystone and Horizon!

 So, from what I'm seeing, it is impossible to build an OpenStack Queens 
All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer...   :-(

 The problem (line 29):

 https://pastebin.com/sns8LG18
[https://pastebin.com/i/facebook.png]

administrative@queens-1:~$ sudo apt install gnocchi-api Reading package lists. 
- Pastebin.com
pastebin.com



 Any workaround or bug reported on Launchpad about this?

 Time for Canonical to provide OpenStack Snap packages!  lol

Thanks!
Thiago


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : 
openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/

Re: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"!

[Tobias Urdin]

I can jump in here as well and say that the Puppet OpenStack project had issue 
with this as well with the UCA Queens release
since we run all services on the same nodes in our CI.

We got help from Corey and James, they added the python-gnocchi (which is py2) 
package which provides the necessary Gnocchi code and
WSGI entry points that we could start using that with Apache2, it just doesn't 
fix the Apache2 config automatically.

Other gnocchi packages like the metricd daemon will still be running python3 
but it won't collide with any packages since it's Apache2 combining that is the 
issue.
You will however need the python3-redis and python3-rados (if you use Ceph) 
packages for the metricd daemon.

The full swap to python3 should be a coordinated bump where it moves all 
packages to python3.
Any changes to the gnocchi-api package does not affect Puppet OpenStack on 
Ubuntu's ability to work as long as python-gnocchi is provided.

Now while we are at it, do you know if python-gnocchi is packaged for bionic? 
Or was it a quick fix for uca/queens only?
Best regards

On 06/05/2018 04:43 PM, Corey Bryant wrote:
Hi Martin,

Thanks for bringing this up. I replied in the bug, but pasting some of my 
response below:

gnocchi-api only supports py3 for now in bionic/queens and above.

Most OpenStack packages in Ubuntu have not yet received py3 support. That is a 
focus for the cosmic cycle. Where possible the plan is to install py2 by 
default and py3 as an alternative to prevent all-in-one issues like this.

In other words, 'sudo apt install python3-keystone keystone' would install 
python3 packages, and (assuming python3-keystone was not already installed) 
'sudo apt install keystone' would install python2 packages.

That's not the case for gnocchi-api, obviously, as it only installs py3 
packages which conflicts with other python packages if and only if you're 
installing on the same machine as other py2 services. Most modern production 
deployments isolate services in one way or another (e.g. containers such as LXD 
or docker) so there's a clear work around.

With that said, we can probably add py2 alternative packages to the Depends for 
gnocchi-api allowing py2 installs, however I seem to remember gnocchi-api was 
forced to move to py3 for a reason. I'm not remembering why though atm.

Thanks,

Corey

On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ 
mailto:thiagocmarti...@gmail.com>> wrote:
Thank you!

On 4 June 2018 at 21:25, pablo brunetti 
mailto:pablobrune...@hotmail.com>> wrote:

Hello,


This bug is confirmed in 
https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992

Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : Bugs : 
gnocchi package : 
Ubuntu
bugs.launchpad.net
Since the two wsgi modules are conflicting, installing gnocchi-api breaks other 
OpenStack services.



Pablo.




De: Martinx - ジェームズ 
mailto:thiagocmarti...@gmail.com>>
Enviado: segunda-feira, 4 de junho de 2018 21:53
Para: openstack@lists.openstack.org; 
James Page
Assunto: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries 
to remove both "keystone" and "openstack-dashboard"!

Hello,

 I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, the 
"gnocchi-api" package tries to uninstall Keystone and Horizon!

 So, from what I'm seeing, it is impossible to build an OpenStack Queens 
All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer...   :-(

 The problem (line 29):

 https://pastebin.com/sns8LG18
[https://pastebin.com/i/facebook.png]

administrative@queens-1:~$ sudo apt install gnocchi-api Reading package lists. 
- Pastebin.com
pastebin.com



 Any workaround or bug reported on Launchpad about this?

 Time for Canonical to provide OpenStack Snap packages!  lol

Thanks!
Thiago


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : 
openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack-dev] OpenStack Queens for Ubuntu 18.04 LTS

[Tobias Urdin]

I got started on kuryr-libnetwork but never finished the init/systemd scripts 
but all dependencies in control file should be ok.

I uploaded it here: https://github.com/tobias-urdin/deb-kuryr-libnetwork (not a 
working package!)

After fixing kuryr-libnetwork one can get starting packaging Zun.


For Qinling you might want kuryr-libkubernetes as well, but I'm unsure.

Best regards

On 04/27/2018 05:56 PM, Corey Bryant wrote:


On Fri, Apr 27, 2018 at 11:23 AM, Tobias Urdin 
mailto:tobias.ur...@crystone.com>> wrote:

Hello,

I was very interested in packaging Zun for Ubuntu however I did not have the 
time to properly get started.

I was able to package kuryr-lib, I've uploaded it here for now 
https://github.com/tobias-urdin/deb-kuryr-lib


Would love to see both Zun and Qinling in Ubuntu to get a good grip on the 
container world :)

Best regards


Awesome Tobias. I can take a closer look next week if you'd like.

Thanks,
Corey

On 04/27/2018 04:59 PM, Corey Bryant wrote:
On Fri, Apr 27, 2018 at 10:20 AM, Hongbin Lu 
mailto:hongbin...@gmail.com>> wrote:
Corey,

Thanks for the information. Would you clarify what is "working packages from 
the community"?

Best regards,
Hongbin

Sorry I guess that comment is probably a bit vague.

The OpenStack packages are open source like many other projects. They're Apache 
2 licensed and we gladly accept contributions. :)

This is a good starting point for working with the Ubuntu OpenStack packages:
https://wiki.ubuntu.com/OpenStack/CorePackages

If you or someone else were to provide package sources for zun that DTRT to 
create binary packages, and if they can test them, then I'd be happy to 
review/sponsor the Ubuntu and cloud-archive uploads.

Thanks,
Corey


On Fri, Apr 27, 2018 at 9:30 AM, Corey Bryant 
mailto:corey.bry...@canonical.com>> wrote:


On Fri, Apr 27, 2018 at 9:03 AM, Hongbin Lu 
mailto:hongbin...@gmail.com>> wrote:
Hi Corey,

What are the requirements to include OpenStack Zun into the Ubuntu packages? We 
have a comprehensive installation guide [1] that are using by a lot of users 
when they were installing Zun. However, the missing of Ubuntu packages is 
inconvenient for our users. What the Zun team can help for adding Zun to Ubuntu.

[1] https://docs.openstack.org/zun/latest/install/index.html

Best regards,
Hongbin

Hi Hongbin,

If we were to get working packages from the community and commitment to test, 
I'd be happy to sponsor uploads to Ubuntu and backport to the cloud achive.

Thanks,
Corey

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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://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://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack-dev] OpenStack Queens for Ubuntu 18.04 LTS

[Tobias Urdin]

Hello,

I was very interested in packaging Zun for Ubuntu however I did not have the 
time to properly get started.

I was able to package kuryr-lib, I've uploaded it here for now 
https://github.com/tobias-urdin/deb-kuryr-lib


Would love to see both Zun and Qinling in Ubuntu to get a good grip on the 
container world :)

Best regards

On 04/27/2018 04:59 PM, Corey Bryant wrote:
On Fri, Apr 27, 2018 at 10:20 AM, Hongbin Lu 
mailto:hongbin...@gmail.com>> wrote:
Corey,

Thanks for the information. Would you clarify what is "working packages from 
the community"?

Best regards,
Hongbin

Sorry I guess that comment is probably a bit vague.

The OpenStack packages are open source like many other projects. They're Apache 
2 licensed and we gladly accept contributions. :)

This is a good starting point for working with the Ubuntu OpenStack packages:
https://wiki.ubuntu.com/OpenStack/CorePackages

If you or someone else were to provide package sources for zun that DTRT to 
create binary packages, and if they can test them, then I'd be happy to 
review/sponsor the Ubuntu and cloud-archive uploads.

Thanks,
Corey


On Fri, Apr 27, 2018 at 9:30 AM, Corey Bryant 
mailto:corey.bry...@canonical.com>> wrote:


On Fri, Apr 27, 2018 at 9:03 AM, Hongbin Lu 
mailto:hongbin...@gmail.com>> wrote:
Hi Corey,

What are the requirements to include OpenStack Zun into the Ubuntu packages? We 
have a comprehensive installation guide [1] that are using by a lot of users 
when they were installing Zun. However, the missing of Ubuntu packages is 
inconvenient for our users. What the Zun team can help for adding Zun to Ubuntu.

[1] https://docs.openstack.org/zun/latest/install/index.html

Best regards,
Hongbin

Hi Hongbin,

If we were to get working packages from the community and commitment to test, 
I'd be happy to sponsor uploads to Ubuntu and backport to the cloud achive.

Thanks,
Corey

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Instances lost connectivity with metadata service.

[Tobias Urdin]

Did some troubleshooting on this myself just some days ago.

You want to check out the neutron-metadata-agent log in 
/var/log/neutron/neutron-metadata-agent.log

neutron-metadata-agent in turn connects to your nova keystone endpoint to talk 
to nova metadata api (nova api port 8775) to get instance information.


I had a issue with connectivity between neutron-metadata-agent and nova 
metadata api causing the issue for me.

Should probably check the nova metadata api logs as well.


Best regards

On 02/26/2018 01:00 PM, Jorge Luiz Correa wrote:
I would like some help to identify (and correct) a problem with instances 
metadata during booting. My environment is a Mitaka instalation, under Ubuntu 
16.04 LTS, with 1 controller, 1 network node and 5 compute nodes. I'm using 
classic OVS as network setup.

The problem ocurs after some period of time in some projects (not all projects 
at same time). When booting a Ubuntu Cloud Image with cloud-init, instances 
lost conection with API metadata and doesn't get their information like 
key-pairs and cloud-init scripts.

[  118.924311] cloud-init[932]: 2018-02-23 18:27:05,003 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: 
request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries 
exceeded with url: /2009-04-04/meta-data/instance-id (Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
[  136.959361] cloud-init[932]: 2018-02-23 18:27:23,038 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: 
request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries 
exceeded with url: /2009-04-04/meta-data/instance-id (Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=17.0)'))]
[  137.967469] cloud-init[932]: 2018-02-23 18:27:24,040 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 120 seconds
[  137.972226] cloud-init[932]: 2018-02-23 18:27:24,048 - 
url_helper.py[WARNING]: Calling 
'http://192.168.0.7/latest/meta-data/instance-id' failed [0/120s]: request 
error [HTTPConnectionPool(host='192.168.0.7', port=80): Max retries exceeded 
with url: /latest/meta-data/instance-id (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused',))]
[  138.974223] cloud-init[932]: 2018-02-23 18:27:25,053 - 
url_helper.py[WARNING]: Calling 
'http://192.168.0.7/latest/meta-data/instance-id' failed [1/120s]: request 
error [HTTPConnectionPool(host='192.168.0.7', port=80): Max retries exceeded 
with url: /latest/meta-data/instance-id (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused',))]

After give up 169.254.169.254 it tries 192.168.0.7 that is the dhcp address for 
the project.

I've checked that neutron-l3-agent is running, without errors. On compute node 
where VM is running, agents and vswitch is running. I could check the namespace 
of a problematic project and saw an iptables rules redirecting traffic from 
169.254.169.254:80 to 
0.0.0.0:9697, and there is a process 
neutron-ns-medata_proxy_ID  that opens that port. So, it look like the 
metadata-proxy is running fine. But, as we can see in logs there is a timeout.

If I restart all services on network node sometimes solves the problem. In some 
cases I have to restart services on controller node (nova-api). So, all work 
fine for some time and start to have problems again.

Where can I investigate to try finding the cause of the problem?

I appreciate any help. Thank you!

- JLC

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] compute nodes down

[Tobias Urdin]

Enable debug in nova.conf and check conductor and compute logs.

Check that your clock is in-sync with NTP or you might experience that the 
alive checks in the database exceeds the service_down_time config value.

On 12/19/2017 12:09 AM, Jim Okken wrote:
hi list,

hoping someone could shed some light on this issue I just started seeing today

all my compute nodes started showing as "Down" in the Horizon -> Hypervisors -> 
Compute Nodes tab


root@node-1:~# nova service-list
+-+--+---+--+-+---++-+
| Id  | Binary   | Host  | Zone | Status  | State | 
Updated_at | Disabled Reason |
+-+--+---+--+-+---++-+
| 325 | nova-compute | node-9.mydom.com  | nova
 | enabled | down  | 2017-12-18T21:59:38.00 | -   |
| 448 | nova-compute | node-14.mydom.com | nova   
  | enabled | up| 2017-12-18T22:41:42.00 | -   |
| 451 | nova-compute | node-17.mydom.com | nova   
  | enabled | up| 2017-12-18T22:42:04.00 | -   |
| 454 | nova-compute | node-11.mydom.com | nova   
  | enabled | up| 2017-12-18T22:42:02.00 | -   |
| 457 | nova-compute | node-12.mydom.com | nova   
  | enabled | up| 2017-12-18T22:42:12.00 | -   |
| 472 | nova-compute | node-16.mydom.com | nova   
  | enabled | down  | 2017-12-18T00:16:01.00 | -   |
| 475 | nova-compute | node-10.mydom.com | nova   
  | enabled | down  | 2017-12-18T00:26:09.00 | -   |
| 478 | nova-compute | node-13.mydom.com | nova   
  | enabled | down  | 2017-12-17T23:54:06.00 | -   |
| 481 | nova-compute | node-15.mydom.com | nova   
  | enabled | up| 2017-12-18T22:41:34.00 | -   |
| 484 | nova-compute | node-8.mydom.com  | nova
 | enabled | down  | 2017-12-17T23:55:50.00 | -   |


if I stop and the start nova-compute on the down nodes the stop will take 
several minutes and then the start will be quick and fine. but after about 2 
hours the nova-compute service will show down again.

i am not seeing any ERRORS in nova logs.

I get this for the status of a node that is showing as "UP"



root@node-14:~# systemctl status nova-compute.service
â nova-compute.service - OpenStack Compute
   Loaded: loaded (/lib/systemd/system/nova-compute.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2017-12-18 21:57:10 UTC; 35min ago
 Docs: man:nova-compute(1)
  Process: 32193 ExecStartPre=/bin/chown nova:adm /var/log/nova (code=exited, 
status=0/SUCCESS)
  Process: 32190 ExecStartPre=/bin/chown nova:nova /var/lock/nova /var/lib/nova 
(code=exited, status=0/SUCCESS)
  Process: 32187 ExecStartPre=/bin/mkdir -p /var/lock/nova /var/log/nova 
/var/lib/nova (code=exited, status=0/SUCCESS)
 Main PID: 32196 (nova-compute)
   CGroup: /system.slice/nova-compute.service
   ââ32196 /usr/bin/python /usr/bin/nova-compute 
--config-file=/etc/nova/nova-compute.conf --config-file=/etc/nova/nova.conf 
--log-file=/var/log/nova/nova-compute.log

Dec 18 22:31:47 node-14.mydom.com 
nova-compute[32196]: 2017-12-18 22:31:47.570 32196 DEBUG 
oslo_messaging._drivers.amqpdriver [req-f30b2331-2097-4981-89c8-acea4a81f7f2 - 
- - - -] CALL msg_id: 2877b9707da144f3a91e7b80e2705fb3 exchange 'nova' topic 
'conductor' _send 
/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:448
Dec 18 22:31:47 node-14.mydom.com 
nova-compute[32196]: 2017-12-18 22:31:47.604 32196 DEBUG 
oslo_messaging._drivers.amqpdriver [-] received reply msg_id: 
2877b9707da144f3a91e7b80e2705fb3 __call__ 
/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:296
Dec 18 22:31:47 node-14.mydom.com 
nova-compute[32196]: 2017-12-18 22:31:47.605 32196 INFO 
nova.compute.resource_tracker [req-f30b2331-2097-4981-89c8-acea4a81f7f2 - - - - 
-] Total usable vcpus: 40, total allocated vcpus: 0
Dec 18 22:31:47 node-14.mydom.com 
nova-compute[32196]: 2017-12-18 22:31:47.606 32196 INFO 
nova.compute.resource_tracker [req-f30b2331-2097-4981-89c8-acea4a81f7f2 - - - - 
-] Final resource view: name=node-14.mydom.com 
phys_ram=128812MB used_ram=512MB phys_disk=6691GB used_disk=0GB total_vcpus=40 
used_vcpus=0 pci_stats=[]
Dec 18 22:31:47 node-14.mydom.com 
nova-compute[32196]: 2017-12-18 22:31:47.610 32196 DEBUG 
oslo_messaging._drivers.amqpdriver 

Re: [Openstack] Restricting volume attachment using policies

[Tobias Urdin]

On 02/20/2017 11:17 AM, Markus Hentsch wrote:
> Am 20.02.2017 um 10:01 schrieb Vincent Gatignol:
>> Le 20/02/2017 à 09:20, Markus Hentsch a écrit :
>>> Hello,
>>>
>>> I'm running a Newton setup where I'm trying to restrict the volume
>>> attachment actions using Nova's policy file.
>>>
>>> I want to check for both the VM ownership as well as the volume
>>> ownership, so that users should be unable to attach volumes if they
>>> aren't the owner of both the VM and the volume.
>>>
>> This is related to https://bugs.launchpad.net/nova/+bug/1539351
>> Openstack policies are mapped at the tenant/project level, not user
>>
>> Regards,
>> Vincent
> Dear Vincent,
>
> thanks for clarifying this!
>
>
> Kind regards,
>
> Markus Hentsch
> Cloud&Heat Technologies
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
Afaik the use of user_id was merged back in until keystone has the support.

See this spec that was merged in Newton.

http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/user-id-based-policy-enforcement.html

https://review.openstack.org/#/q/topic:bp/user_id_based_policy_enforcement,n,z


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Where is Ceilometer endpoint? Is it with Gnocchi now!?

[Tobias Urdin]

Hello,

You are correct, please report a bug by clicking the "bug report" link on that 
page.
https://docs.openstack.org/project-install-guide/telemetry/draft/install-base-ubuntu.html

Best regards

On 02/17/2017 06:14 AM, Martinx - ? wrote:
Guys,

 According to the new doc:

 
https://docs.openstack.org/project-install-guide/telemetry/draft/install-base-ubuntu.html

 There are no instructions to create the Ceilometer endpoint... Is this correct?

 If yes, how to configure Aodh when with a Ceilometer that have no endpoint?

 Right now, my aodh-evaluator.log prints this:

---
ERROR aodh.evaluator.threshold EndpointNotFound: internalURL endpoint for 
metering service in ca-east-1 region not found
---

 Any tips?

Thanks!
Thiago

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] nagios tips

[Tobias Urdin]

Hello Remo,

What kind of help are you seeking? I assume it's OpenStack related and
not really the Nagios part.

Here are the nagios plugins we are using to monitor our production cloud
running Liberty https://github.com/crystone/openstack-monitoring


Best regards


On 10/11/2016 06:12 AM, Remo Mattei wrote:
> Hello guys, does anyone have any guides for nagios. I have installed while 
> back, but I need to add it in one of our test lab. 
>
> Thanks
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Multiple availability zones

[Tobias Urdin]

Yes because a availability zone does not "belong" to anything.

It's simply a group of resources defined in your nova database to make
scheduling decisions.

Best regards


On 09/29/2016 03:08 PM, Turbo Fredriksson wrote:
> On Sep 29, 2016, at 8:52 AM, Tobias Urdin wrote:
>
>> If I have understood it correctly your primary question is about
>> availability zones.
> Technically I guess that's right, but not so much about what it/they
> are and how they're used, but more like "can a controller manage multiple
> zones"..
>
> And with "a controller" I'm thinking Neutron, Keystone, Cinder etc, etc.
> --
> You know, boys, a nuclear reactor is a lot like a woman.
> You just have to read the manual and press the right buttons
> - Homer Simpson
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Provisioning VMs in Openstack cluster

[Tobias Urdin]

Can you post your logs and configs.
Please check where you think it's slow, if you for example provision
only a volume is it slow there?

To just follow my hunch, have you configured vif_plugging_timeout in
nova.conf or is it the default value of 300?
We have vif_plugging_timeout=5, you should try that. We are live on
Liberty and are slowly upgrading to Mitaka for reference.

Best regards

On 09/28/2016 10:52 PM, Leon Liu wrote:
> OK, thanks. I better check that more  
>
> -Original Message-
> From: Turbo Fredriksson [mailto:tu...@bayour.com] 
> Sent: Wednesday, September 28, 2016 4:04 PM
> To: Leon Liu
> Cc: openstack@lists.openstack.org
> Subject: Re: [Openstack] Provisioning VMs in Openstack cluster
>
> But what I _think_ I've seen (can't be absolutly sure, because I never
> investigated in detail) is that Cinder seems to be 'idling' a little to
> much.
>
> It starts creating the volume, then waits for a while, then starts sending
> the image to the volume, then waits and waits, and then the process
> continues.
>
> All the services seems to be doing this waiting. It's like they only do
> things when the scheduler tells them, not when the service is done with one
> task..=
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Multiple availability zones

[Tobias Urdin]

Hello Turbo,
If I have understood it correctly your primary question is about
availability zones.

There is no requirements for running a availability zone, it's simply a
way to group compute resources into a zone.
After users can select where the resources should be deployed.

As compared to having regions where it's more two clouds having the same
Keystone for authentication.

Availability zones is simply a logical separation of your resources
compared to host aggregates your resources can only be in one
availability zone but have multiple host aggregates. See the aggregate
documentation and perhaps that clears it up more than my messy writing.
http://docs.openstack.org/developer/nova/aggregates.html

Forgive me if I missed some questions or statements in your wall of
text, it's early in the morning :)
Best regards

On 09/28/2016 09:18 PM, Turbo Fredriksson wrote:
> Thanx everyone in helping me figure out how I wanted my multiple
> controller nodes setup - using keepalived and load balance the
> services with that is well under way and so far it looks like
> it's working.
>
> I still have to fine-tune and finish that work of. But modifying
> my setup scripts etc to set this up (the physical hosts is setup
> using PXE and a bunch of scripts etc; the VMs is setup using
> puppet - it's to late to puppetize the physical nodes, but it's
> fine, PXE and the scripts let me destroy a node and just recreate
> it in minutes), lead me directly to another TODO I've had for a while,
> which now require a decision.
>
>
> My blade center have sixteen half-height nodes (eight in two rows),
> where I've decided to have the first node as a Control node (that's
> the one that's been up and running for months now), the following
> seven nodes in the first row as internal (for my own personal use)
> compute nodes. Those nodes would be dedicated for my infrastructure.
> Such as LDAP, kerberos, SMTP, VoIP server etc, etc.
>
> Those seven is also fully working.
>
> Technically I only seem to need three nodes for all of that, but
> that would mean that they would be quite cramped (I don't have
> that much memory in the machines unfortunately). And I'd loose
> out on having services on different physical hosts. Also, possible
> future need makes it reasonable to dedicate all seven to my
> infrastructure.
>
>
> Then node nine (first node on the second row) would then be my
> second control node (this is the one I'm setting up now) and then
> seven physical nodes for "miscellaneous" (mostly my development
> and test machines of different operating systems, distributions
> and versions, friends VMs etc, etc).
>
>
> So what this means is that having two different availability zones,
> first row is now named 'nova' (which is the default in OS, and it
> makes sense to keep that) and the second .. "user" (or whatever)
> seems like a reasonable approach.
>
> From what I understand of AZs, is that if I create an instance,
> I need to specify the AZ (I'm using Heat and extremely early on
> in my OS setup, I created templates and worked around the need
> to specify the AZ - my template use that for me now) and the
> instance will ONLY be started in that specified AZ. Which helps
> things being created in the right place.
>
> Eventually, I probably have to figure out a way to make sure
> that only I can create instances in the 'nova' AZ, but that
> can be an exercise for another day..
>
>
> However, and here comes the question after a long babbling of
> what I'm up to, the two controller nodes need to be able to
> manage _both_ availability zones! I can not (do not want to)
> waste more resources. Technically, I don't really _NEED_ two
> controllers, but for at least a rudimentary high-availability
> (which is, because they're on the same network, on the same
> switch, on the same breaker, the same power cable etc, etc,
> is only imaginary and one can still handle the load just fine,
> even with the possible future use, having two makes at least
> _some_ shred of 'good idea'), I've already dedicated these two
> physical nodes for that.
>
> Is this possible? Can a controller node (i.e., a physical node
> that runs EVERYTHING but Nova - aodh, barbican, ceilometer, cinder,
> etc, etc, etc!) also control multiple availability zones?
>
> They of course could have their own separate _default_ AZ, even
> though I'm not sure that is needed.
>
>
> The first objection I can think of is the networking - where
> do the network go in/out of OS if the primary controller dies?
> And how do I solve that? Currently, everything goes in and out
> via the first control node, which seems to be just fine. So what
> happens to the traffic if/when that dies? Will OS (Neutron)
> automatically use the second controller?


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] retrieve all instances whatever tenant/user via python SDK

[Tobias Urdin]

Hello,

Auth using the admin user then list all instances in all tenants, should be 
something like:
client.servers.list(search_opts={'all_tenants': 1})

You should search, there is a lot of resources online that could help you out.
For example if you would have searched: 
https://ask.openstack.org/en/question/50087/list-all-servers-with-python-nova-client/

Best regards

On 06/08/2016 03:29 PM, Jean-Pierre Ribeauville wrote:
Hi all,

By running this piece if code :

.
def get_nova_credentials_v2():
d = {}
d['version'] = '2'
d['username'] = os.environ['OS_USERNAME']
d['api_key'] = os.environ['OS_PASSWORD']
d['auth_url'] = os.environ['OS_AUTH_URL']
d['project_id'] = os.environ['OS_TENANT_NAME']
return d

credentials = get_nova_credentials_v2()
nova_client = Client(**credentials)

print(nova_client.servers.list())
..

I'm able to retrieve the instances list when specifying the tenant and username 
to whom the instances < belong >.

As I want to retrieve all instances , I tried to use admin as tenant and user , 
then no instance are found ( all my instances are under "demo").

Via Horizon , all instances are retrievable under admin .

Did I miss something  ?

Thx for help.

Regards,

Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

[axway_logo_tagline_87px]


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Using Python SDK to retrieve cloud topology

[Tobias Urdin]

Hello Jean-Pierre,

Yes you can.
You can gather or control all parts of OpenStack using the REST API:s

Best regards

#!/usr/bin/env python

from novaclient import client

nova = client.Client(2, "adminuser", "passwordhere", "adminproject", 
"http://controller:35357/v2.0";)

print "Hypervisors:"
print nova.hypervisors.list()

print "Aggregates:"
print nova.aggregates.list()

print "Availability zones:"
print nova.availability_zones.list()

On 06/07/2016 04:16 PM, Jean-Pierre Ribeauville wrote:
Hi,

By using OpenStack Python SDK, is it possible to retrieve such things as 
hypervisors , aggregate  and availability zones list?
Thx for help.

Regards,

Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

[axway_logo_tagline_87px]


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Enabling volume usage audit - cinder

[Tobias Urdin]

You must add a cron job for the cinder-volume-usage-audit, like this.

root@cinder:~# cat /etc/cron.d/cinder-volume-usage-audit
*/30 * * * * root (PYTHONIOENCODING=utf-8 /usr/bin/cinder-volume-usage-audit 
1>> /var/log/cinder/cinder-volume-usage-audit-`date +\%Y\%m\%d`.log 2>&1)

That will run each 30 minutes.

Best regards

On 06/07/2016 10:04 AM, murali wrote:
Hello guys,

I am using Devstack Liberty version.

I need to use the volume usage audit option which is available in cinder.

I can be able to succesfully execute the cinder-volume-usage-audit command in 
my commandline.

I need to make it run periodically.

So that I can be able to see that adding a config entry will work.

I have added the entry in config file as follows:

volume_usage_audit_period=hour

But it seems not generating the report. I have added the entry in to config 
file and then restarted cinder services.

Is there anything else I am missing.

Someone let me know the way how we can achieve this ?

Any comments or suggestions?

Regards,

Murali.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] OpenStack Python SDK

[Tobias Urdin]

Hello Jean-Pierre,

All aspects of OpenStack is fronted with a API service.
Yes there are python clients/bindings for all projects.

Best regards
Tobias

On 04/19/2016 11:57 AM, Jean-Pierre Ribeauville wrote:
Hi

Does it exist a functionally equivalent to OVIRT Python SDK   on OpenStack ?


Thx for help.

Regards,

Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

[axway_logo_tagline_87px]


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Cinder quota-show demo error

[Tobias Urdin]

Hello Remo,

I think you are feeling this bug.
https://bugs.launchpad.net/cinder/+bug/1516085

Quota won't work if you're running Keystone on another machine than the 
cinder-api unless the keymgr.encryption_auth_url config option is populated 
because
the default value for that option is to use the v3 endpoint on localhost for 
Keystone.

You should see this if you enable debug for cinder-api
Caught error: Authorization failed: Unable to establish connection to 
http://localhost:5000/v3/auth/tokens

Hope this helps you, this was patched but I don't know if it's released yet, 
perhaps not in the distro you are using.
Best regards.

On 01/20/2016 08:49 PM, Remo Mattei wrote:

Hello all, does anyone have an suggestion on this error?

[root@osc1 ~(keystone_admin)]# cinder quota-show demo
ERROR: The server has either erred or is incapable of performing the requested 
operation. (HTTP 500) (Request-ID: req-4a681bb0-a0b5-4325-8c12-3f48659a42f1)


[root@osc1 ~(keystone_admin)]# cinder list
+--+---+--+--+--+-+--+-+-+
|  ID  |   Status  | Migration Status | Name | 
Size | Volume Type | Bootable | Multiattach | Attached to |
+--+---+--+--+--+-+--+-+-+
| 5a5558a6-8a7b-46d8-8db6-2cdfee46fef0 | available |- |  -   |  
1   |  -  |  false   |False| |
| a3204f4f-142d-4a3e-9007-9fa149302f08 | available |- |  -   |  
1   |  -  |  false   |False| |
| aac3b72a-e9ca-4e4a-94ce-2b03532eb516 | available |- | remo |  
1   |  -  |  false   |False| |
| e8aa977c-3802-45cc-b700-0b7778840318 | available |- | test |  
1   |  -  |  false   |False| |
+--+---+--+--+--+-+--+-+--+


I can attached and create volumes no problems at all.

in the cinder-api logs I get just a warning which is ok.

WARNING keystonemiddleware.auth_token [-] Use of the auth_admin_prefix, 
auth_host, auth_port, auth_protocol, identity_uri, admin_token, admin_user, adm
in_password, and admin_tenant_name configuration options is deprecated in favor 
of auth_plugin and related options and may be removed in a future release.
2015-12-18 13:16:11.639 3403 WARNING oslo_log.versionutils [-] Deprecated: 
RequestBodySizeLimiter() is deprecated as of Kilo in favor of 
oslo_middleware.RequestBodySizeLimiter and
may be removed in Mitaka.


Thanks,
Remo
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : 
openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack