On 6/14/17, 6:00 PM, "Abhishek Kane" wrote:
>Thank you for the comments Emilien!
>
>Updated as per your suggestions:
>puppet-veritas-hyperscale:
>https://github.com/abhishek-kane/puppet-veritas-hyperscale
>
>Also, please find the inline replies to your comments.
>
Thank you for the comments Emilien!
Updated as per your suggestions:
puppet-veritas-hyperscale:
https://github.com/abhishek-kane/puppet-veritas-hyperscale
Also, please find the inline replies to your comments.
We had been able to call the old puppet modules (which had scripts) using the
On Wed, Jun 7, 2017 at 10:38 AM, Abhishek Kane
wrote:
> Hi,
>
> On cinder node- we need to modify the cinder.conf. We don’t change any config
> apart from this. We want to keep the config changes in heat template, package
> installation in puppet, and trigger rest of
Updated https://github.com/abhishek-kane/puppet-veritas-hyperscale with the
attempts to reuse puppet modules for keystone, rabbitmq and nova_flavor. Still
doing some operation via scripts.
Regards.
On 6/7/17, 8:08 PM, "Abhishek Kane" wrote:
Hi,
On
Hi,
On cinder node- we need to modify the cinder.conf. We don’t change any config
apart from this. We want to keep the config changes in heat template, package
installation in puppet, and trigger rest of the operations via Horizon (as it’s
done today). We are also trying to get rid of the
On Thu, Jun 1, 2017 at 3:47 PM, Abhishek Kane wrote:
> Hi Emilien,
>
> The bin does following things on controller:
> 1. Install core HyperScale packages.
Should be done by Puppet, with Package resource.
> 2. Start HyperScale API server
Should be done by Puppet, with
Hi Emilien,
The bin does following things on controller:
1. Install core HyperScale packages.
2. Start HyperScale API server
3. Install UI packages. This will add new files to and modify some existing
files of Horison.
4. Create HyperScale user in mysql db. Create database and dump config. Add