mitakauser's profile - activity

2018-04-13 02:57:32 -0600 received badge  Student (source)
2017-01-03 03:20:01 -0600 received badge  Famous Question (source)
2016-09-19 12:14:37 -0600 received badge  Notable Question (source)
2016-09-15 04:27:11 -0600 received badge  Popular Question (source)
2016-09-14 14:08:16 -0600 asked a question Magnum vm instance can ping controller ip but can't resolve it by hostname to notify heat of status

Hi ,

We're currently implementing a magnum bay deployment for testing purposes. So far we've been able to create a bay successfully but not without a few quirks. I know that magnum calls the heat api to create the whole bay (master, minion, health monitor,lbaas,etc). I was getting curious as to why after 1 hour the bay status remained in "Create in Progress" and only one instance was created (baymodel config with 1 master and 1 minion) so I dove into the system logs (fedora 23) via journalctl and one thing caught my attention. This line in particular:

Aug 26 01:16:01 fe-tdlnn6z37o-0-j4pmkkqrwsjx-kube-master-mb5kf6rv4vzp.novalocal wc-notify[1580]: okcurl -i -X POST -H 'X-Auth-Token: gAAAAABXv5ZTcss3qrjgtVFM-f5zxrrEEC-Mx3Qbx7O_1fJUeqkkn0lM5omb9U3UvM-NBHS0pKKFcRJp0Apa7Zxz_MGBDssRdLUSA-e13hoEhBFOf-r3ZrXZ_4AegdbziOYSm6C23cYZZW_HU-pu2Fs6vpe4taFP_HaKOBHGdVA9wiaoq7qC99E' -H 'Content-Type: application/json' -H 'Accept: application/json' **http://controller:8004/v1/9d7a25b6e7a74bce9fc09f06a3b0e258/stacks/fedora-23-bay-76m7za4mekfi-kube_masters-mjtdlnn6z37o-0-j4pmkkqrwsjx/d558128b-96e3-4ddb-a8ba-f464995fd118/resources/master_wait_handle/signal** --data-binary '{"status": "SUCCESS"}'

In the magnum heat template directory (controller node) I found a script that makes this call, I'm assuming that this is to notify heat when the master node (and minion) creation was successful so heat can update its status back to cli/horizon. So from the instance I tried to ping controller first by ip address which was successful and then by hostname "controller" with output "unknown host controller". Only after I put in the entry in the /etc/hosts file (vm instance) the aforementioned call to the controller was able to notify heat of the master creation (same case as with the minions). My question is ...is there a way to automate the name resolving for controller hostname without having to ssh into each node instance and modifying /etc/hosts?. Unless of course I'm missing something else here in which case any pointers would be greatly appreciated. Please also let me know if you need more information I'll be happy to provide it.

I followed this guide for installing magnum

http://docs.openstack.org/developer/m...

Regards

2016-05-11 09:18:27 -0600 received badge  Enthusiast
2016-05-09 11:23:43 -0600 commented answer Ceilometer - Keystone authentication status code 401

@todotani have you created the keystone API V3 endpoints?. I followed the Ubuntu installation guide but CentOS should be the same. http://docs.openstack.org/mitaka/inst...

2016-05-07 04:12:48 -0600 received badge  Teacher (source)
2016-05-07 04:12:48 -0600 received badge  Self-Learner (source)
2016-05-06 05:38:49 -0600 received badge  Famous Question (source)
2016-05-04 13:40:46 -0600 answered a question Ceilometer - Keystone authentication status code 401

I was able to resolve my issue by migrating the ceilometer auth to keystone to v3. This is how the ceilometer service_credentials section looks now

[service_credentials]
auth_url = http://controller:5000/v3
username = ceilometer
tenant_name = service
password = xxxxxx
interface = internalURL
region_name = RegionOne
project_name = service
project_domain_id = xxxxxxxx
user_domain_id = xxxxxxxx
auth_type = password

With this configuration I was able to authenticate to keystone successfully.

2016-05-02 17:45:46 -0600 received badge  Editor (source)
2016-05-02 17:30:26 -0600 received badge  Notable Question (source)
2016-05-02 12:39:38 -0600 received badge  Popular Question (source)
2016-05-02 12:02:11 -0600 commented answer Ceilometer - Keystone authentication status code 401

I have followed your suggestion by creating a keystonerc file with the values in the service credentials section ceilometer.conf and got the same error ERROR (Unauthorized): The request you have made requires authentication. (HTTP 401) it seems parameters are missing...similar to adminopenrc?

2016-05-02 11:58:14 -0600 commented answer Ceilometer - Keystone authentication status code 401

Thanks @yprokule . In the ceilometer.conf there's the auth_uri and then the auth_url definitions. At first I was confused as well. The installation was deployed manually and indeed I have a dedicated compute node for my openstack setup.

2016-04-29 22:28:23 -0600 asked a question Ceilometer - Keystone authentication status code 401

Hi everyone,

At work we've been trying to figure out how to get Ceilometer on the compute node to authenticate agasint Keystone but to no avail.

Here's the output of the keystone-wsgi-public log (controller node)

2016-04-29 18:54:19.074 26606 INFO keystone.common.wsgi [req-3e3fab30-5b37-4a22-8ad1-9b42bc46780d - - - - -] POST http://controller:5000/v2.0/tokens
2016-04-29 18:54:19.081 26606 WARNING keystone.common.wsgi [req-3e3fab30-5b37-4a22-8ad1-9b42bc46780d - - - - -] Authorization failed. The request you have made requires authentication. from xx.xx.xx.xx
2016-04-29 18:54:19.090 26604 DEBUG keystone.middleware.auth [req-08ae6a8a-4584-4033-9bd0-904d20cb6f1f - - - - -] There is either no auth token in the request or the certificate issuer is not trusted. No auth context will be set. _build_auth_context /usr/lib/python2.7/dist-packages/keystone/middleware/auth.py:71

And here's the output of the ceilometer-compute.log (compute node)

2016-04-29 18:35:26.708 24510 DEBUG ceilometer.pipeline [req-34e15155-ebb3-4a29-88ab-c6869c6693c8 admin - - - -] Polling config file: /etc/ceilometer/pipeline.yaml _setup_polling_manager /usr/lib/python2.7/dist-packages/ceilometer/pipeline.py:804
2016-04-29 18:35:26.723 24510 INFO ceilometer.pipeline [req-34e15155-ebb3-4a29-88ab-c6869c6693c8 admin - - - -] Pipeline config: {'sources': [{'interval': 600, 'meters': ['*'], 'name': 'meter_source', 'sinks': ['meter_sink']}, {'interval': 600, 'meters': ['cpu'], 'name': 'cpu_source', 'sinks': ['cpu_sink', 'cpu_delta_sink']}, {'interval': 600, 'meters': ['disk.read.bytes', 'disk.read.requests', 'disk.write.bytes', 'disk.write.requests', 'disk.device.read.bytes', 'disk.device.read.requests', 'disk.device.write.bytes', 'disk.device.write.requests'], 'name': 'disk_source', 'sinks': ['disk_sink']}, {'interval': 600, 'meters': ['network.incoming.bytes', 'network.incoming.packets', 'network.outgoing.bytes', 'network.outgoing.packets'], 'name': 'network_source', 'sinks': ['network_sink']}], 'sinks': [{'publishers': ['notifier://'], 'transformers': None, 'name': 'meter_sink'}, {'publishers': ['notifier://'], 'transformers': [{'name': 'rate_of_change', 'parameters': {'target': {'scale': '100.0 / (10**9 * (resource_metadata.cpu_number or 1))', 'type': 'gauge', 'name': 'cpu_util', 'unit': '%'}}}], 'name': 'cpu_sink'}, {'publishers': ['notifier://'], 'transformers': [{'name': 'delta', 'parameters': {'target': {'name': 'cpu.delta'}, 'growth_only': True}}], 'name': 'cpu_delta_sink'}, {'publishers': ['notifier://'], 'transformers': [{'name': 'rate_of_change', 'parameters': {'source': {'map_from': {'name': '(disk\\.device|disk)\\.(read|write)\\.(bytes|requests)', 'unit': '(B|request)'}}, 'target': {'type': 'gauge', 'map_to': {'name': '\\1.\\2.\\3.rate', 'unit': '\\1/s'}}}}], 'name': 'disk_sink'}, {'publishers': ['notifier://'], 'transformers': [{'name': 'rate_of_change', 'parameters': {'source': {'map_from': {'name': 'network\\.(incoming|outgoing)\\.(bytes|packets)', 'unit': '(B|packet)'}}, 'target': {'type': 'gauge', 'map_to': {'name': 'network.\\1.\\2.rate', 'unit': '\\1/s'}}}}], 'name': 'network_sink'}]}
2016-04-29 18:35:26.724 24510 INFO ceilometer.pipeline [req-34e15155-ebb3-4a29-88ab-c6869c6693c8 admin - - - -] detected decoupled pipeline config format
2016-04-29 18:35:26.728 24510 DEBUG keystoneauth.identity.v2 [req-34e15155-ebb3-4a29-88ab-c6869c6693c8 admin - - - -] Making authentication request to http://controller:35357/v2.0/tokens get_auth_ref /usr/lib/python2.7/dist-packages/keystoneauth1/identity/v2.py:63
2016-04-29 18:35:29.135 24510 DEBUG keystoneauth.session [req-34e15155-ebb3-4a29-88ab-c6869c6693c8 admin - - - -] Request returned failure status: 401 request /usr/lib/python2.7/dist-packages/keystoneauth1/session.py:466
2016-04-29 18:35:29.136 24510 ERROR ceilometer.nova_client [req-34e15155-ebb3-4a29-88ab-c6869c6693c8 admin - - - -] The request you have made requires authentication. (HTTP 401) (Request-ID: req-128a4b95-3d5d-486c-bab1-1a9be6f676d1)
2016-04-29 18:35:29.136 24510 ERROR ceilometer.nova_client Traceback (most recent call last):
2016-04-29 18:35:29.136 24510 ERROR ceilometer.nova_client   File "/usr/lib/python2.7/dist-packages/ceilometer/nova_client.py", line 52, in with_logging
2016-04-29 18:35:29.136 24510 ERROR ceilometer.nova_client     return func(*args ...
(more)