Yes, sure. This has to be the problem. We are logging with a wrong user/password for sure. From the fuel plugin we call the midonet api using the astute config files:
class {'::midonet::midonet_api': zk_servers => $zoo_ips, keystone_auth => true, keystone_host => $::fuel_settings['management_vip'], keystone_admin_token => $::fuel_settings['keystone']['admin_token'], bind_address => $::ipaddress_br_mgmt, api_ip => $::fuel_settings['public_vip'], api_port => '8081' }
so maybe the problem resides on the midonet puppet module.
Yes, sure. This has to be the problem. We are logging with a wrong user/password for sure. From the fuel plugin we call the midonet api using the astute config files:
class {'::midonet: :midonet_ api': settings[ 'management_ vip'], admin_token => $::fuel_ settings[ 'keystone' ]['admin_ token'] , br_mgmt, settings[ 'public_ vip'],
zk_servers => $zoo_ips,
keystone_auth => true,
keystone_host => $::fuel_
keystone_
bind_address => $::ipaddress_
api_ip => $::fuel_
api_port => '8081'
}
so maybe the problem resides on the midonet puppet module.