Head in the Clouds

ahsalkeld.wordpress.com · English

Just another WordPress.com site

rss2 wordpress content media slash wfw atom dc sy

Open the feed

https://ahsalkeld.wordpress.com/feed/

Last post: Sep 25, 2014
Posts in 24 h · 7 days · 30 days: 0 · 0 · 0
Our last check: Answering
Served from: United States
Text score at discovery: 3,863
Format: rss2
Features in the feed: content, media, slash, wfw, atom, dc, sy
Community: wordpress

Posts

What our queue read from this feed. Open one to read it here, or go to the site that published it.

Deap dive into using Heat Alarms
Sep 25, 2014 · original
So this is just some output from me debugging how Heat’s alarms work with the other parts of OpenStack (warts-n-all). First some histroy Way back, Heat needed alarms to be able to do autoscaling (because it is really useful). The only problem was we didn’t have Ceilometer back then. So we wrote a minimalist version of Cloud Watch, it was not suposed to last very long as we fully expected some monitoring-aas to come along. Alas, it has lasted a lot longer then expected. Also note that we didn’t have Alarms based on notifcations at this point so all metrics were generated by an agent (cfn-push-stats). Using Cloud Watch alarms First off how you can choose the implementation (Ceilometer/Heat). We use the global environment to configure this. Look in /etc/heat/environment.d/default.yaml Just uncomment the one you want (We HIGHLY recommend Ceilometer). resource_registry: # Choose your implemen
How to profile Heat using OSprofile
Sep 4, 2014 · original
The OpenStack Heat project has been having some scaling issues, and it really helps knowing where your problems are before trying to solve them. So to help out here are the instructions to get osprofiler ( https://github.com/stackforge/osprofiler/ ) working with Heat (and the other projects that have support for it). Note: I am assuming you are using devstack Once the inflight patches have landed this will be a lot easier! Go to the base directory of your projects. cd cinder git pull echo -e "[profiler]\nprofiler_enabled = True\n" /etc/cinder/cinder.conf cd ../python-cinderclient git review -d 103359 cd ../nova git review -d cp etc/nova/api-paste.ini /etc/nova/ echo -e "[profiler]\nprofiler_enabled = True\n" /etc/nova/nova.conf cd ../python-novaclient git review -d cd ../heat git review -d 118115 cp etc/heat/api-paste.ini /etc/heat/ echo -e "[profiler]\nprofiler_enabled = True\ntrace_sql
How to get Heat to work with a remote Openstack.
Oct 24, 2011 · original
Say you have a remote/public install of Openstack and you want to use a local install of Heat to talk to it. I find this handy when developing, as the remote Openstack can be kept stable and is not effected by changes made to the development machine. So lets say you have 2 machines: “rock” ip == 192.168.1.88 (used for base Openstack services) “hack” ip == 192.168.1.77 (used for Heat development) Install your Openstack as normal on “rock”. I used devstack to install Heat on “hack”. My localrc looked like this: HEAT_STANDALONE=True KEYSTONE_AUTH_HOST=192.168.1.88 KEYSTONE_AUTH_PORT=35357 KEYSTONE_AUTH_PROTOCOL=http KEYSTONE_SERVICE_HOST=$KEYSTONE_AUTH_HOST KEYSTONE_SERVICE_PORT=$KEYSTONE_AUTH_PORT KEYSTONE_SERVICE_PROTOCOL=$KEYSTONE_AUTH_PROTOCOL MY_PASSWORD=abetterpasswordthanthis DATABASE_PASSWORD=$MY_PASSWORD RABBIT_PASSWORD=$MY_PASSWORD disable_all_services ENABLED_SERVICES=qpid enable

Discovered by the rss-feed-index crawler, which checks each feed at most once a month.

Same record as JSON: https://api.agentalog.com/api/feeds/fd_ahsalkeld_wordpress_com_6f7224e9b7cab639. More from this site: ahsalkeld.wordpress.com in the Feeds tab.