Following the devtest workflow, and adding "tuskar" to the undercloud via UNDERCLOUD_DIB_EXTRA_ARGS, I can see that the tuskar-api service is installed.
Running >> ls /etc/tuskar in the undercloud gives:
nova_overcloud_config.yml policy.json tripleo-heat-templates tuskar.conf
so the tripleo-image-templates are there.
Testing this out on Fedora 19, I had to ssh to the undercloud and start the tuskar-api service manually. Once the service was started, I tried some curl examples against it. Those errored out - however checking with one of the api developers, it seems that the api is in flux right now - with expected errors.
I can try this test again once the api is in working order.
Service status output once stated:
tuskar-api.service - tuskar-api Service
Loaded: loaded (/usr/lib/systemd/system/tuskar-api.service; disabled)
Active: active (running) since Wed 2014-01-29 12:47:24 UTC; 1h 0min ago
Main PID: 17280 (tuskar-api)
CGroup: /system.slice/tuskar-api.service
└─17280 /opt/stack/venvs/tuskar/bin/python /opt/stack/venvs/tuskar/bin/tuskar-api --config-dir /etc/tuskar
I've been working on verifying whether or not this has been fixed.
Looking at: tripleo- image-elements/ elements/ tuskar/ element- deps, tripleo- heat-templates is *not* listed. However, looking at the README.md Configuration section in https:/ /github. com/openstack/ tripleo- image-elements/ tree/master/ elements/ tuskar, the defaults described work out.
Following the devtest workflow, and adding "tuskar" to the undercloud via UNDERCLOUD_ DIB_EXTRA_ ARGS, I can see that the tuskar-api service is installed.
Running >> ls /etc/tuskar in the undercloud gives: config. yml policy.json tripleo- heat-templates tuskar.conf image-templates are there.
nova_overcloud_
so the tripleo-
Testing this out on Fedora 19, I had to ssh to the undercloud and start the tuskar-api service manually. Once the service was started, I tried some curl examples against it. Those errored out - however checking with one of the api developers, it seems that the api is in flux right now - with expected errors.
I can try this test again once the api is in working order.
Service status output once stated: systemd/ system/ tuskar- api.service; disabled) slice/tuskar- api.service venvs/tuskar/ bin/python /opt/stack/ venvs/tuskar/ bin/tuskar- api --config-dir /etc/tuskar
tuskar-api.service - tuskar-api Service
Loaded: loaded (/usr/lib/
Active: active (running) since Wed 2014-01-29 12:47:24 UTC; 1h 0min ago
Main PID: 17280 (tuskar-api)
CGroup: /system.
└─17280 /opt/stack/