on a compute instance to
listen on an unix socket while still being able to communicate with the Heat
engine. I have created a blueprint to capture this proposal:
https://blueprints.launchpad.net/heat/+spec/software-config-docker
Any input on this proposal is welcome.
Thanks everyone!
-Andrew
. Docker already has support for mapping host to container
ports, so the software config agent would have to just pass those options
along.
-Andrew
On 5/20/14 4:16 PM, andrew plunk andrewdev...@gmail.com wrote:
Excerpts from Andrew Plunk's message of 2014-05-20 13:49:58 -0700:
No Problem
. human readable name:
RAXHeatCI
4. email
heat-...@lists.rackspace.com
Thank you for your help!
-Andrew Plunk
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Excerpts from Randall Burt's message of 2013-12-05 09:05:44 -0800:
On Dec 5, 2013, at 10:10 AM, Clint Byrum clint at fewbar.com
wrote:
Excerpts from Monty Taylor's message of 2013-12-04 17:54:45 -0800:
Why not just use glance?
I've asked that question a few times, and I think I can
once and only once or display this output with a flag after the first
time.
-Andrew Plunk
From: Zane Bitter [zbit...@redhat.com]
Sent: Tuesday, November 12, 2013 7:32 AM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [Heat] Locked Outputs
On 07
Alright.
The problem:
If a program generates a password, and displays it on a screen over and over
again, it is more susceptible to being compromised.
Possible solutions:
1).Provide a way to limit the availability of stack outputs returned from heat.
2).Provide
view_once: True
Any feedback would be appreciated. Thanks!
-Andrew Plunk
___
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
