nstack.org/#/c/307658/
>
> Could you, please, try to apply this patch and reply does it help or not.
>
> On Fri, Apr 22, 2016 at 5:40 PM, Guillaume Thouvenin
> wrote:
>
>> Hello,
>>
>> deployment_tasks.yaml for the fuel-plugin-lma-collector plugin has this
>>
Hello,
deployment_tasks.yaml for the fuel-plugin-lma-collector plugin has this
task definition:
- id: lma-aggregator
type: puppet
version: 2.0.0
requires: [lma-base]
required_for: [post_deployment_end]
role: '*'
parameters:
puppet_manifest: puppet/manifests/aggregator.pp
puppe
Hi guys,
And also for 7.0 there is a spec in review [1] about custom labels that
may be interesting to differentiate nodes with the same role if labels are
exposed via the astute.yaml.
Regards,
[1] https://review.openstack.org/#/c/184076/
On Thu, Jun 25, 2015 at 12:47 PM, Andrey Danin wrote:
On Wed, Sep 10, 2014 at 2:40 PM, Tomasz Napierala
wrote:
>
> Regarding
> After careful consideration, I think that for 6.0 we will only be able to
> implement [2] with limited functionality. In terms of certificate
> management, we could offer uploading customer generated cert (and maybe
> provid
I think that the management of certificates should be discussed in the
ca-deployment blueprint [3]
We had some discussions and it seems that one idea is to use a docker
container as the root authority. By doing this we should be able to sign
certificate from Nailgun and distribute the certificate
On Thu, Aug 21, 2014 at 5:02 PM, Mike Scherbakov
wrote:
>
>
> Guillaume, do I understand right that without implementation of
> https://blueprints.launchpad.net/fuel/+spec/ca-deployment, SSL support
> will not be fully automated? And, consequently, we can not call it as
> complete production read
Hi all,
I wrote a "design" to enable SSL between external client and OpenStack
public endpoints that provide APIs on public network. This design is
available for reviewing here: https://review.openstack.org/#/c/102273/
Of course all comments are welcome :)
I also started to work on puppet manif
