Hi Jim, There are a couple of ways to approach your problem: 1. Implement Fuel Plugin, where the plugin would automatically override changes done by Fuel core tasks [1], you can override or skip any task from deployment graph. 2. Fix puppet manifests in place, the manifests which are used for deployment are located in "/etc/puppet/" directory on Fuel Master node, during the deployment they are synced to OpenStack nodes via rsync. You should grep for nova_config, keystone_config, etc, to see where the parameters your are looking for are located, do not forget to put it under git so you can keep track of your changes.
Thanks, [1] https://docs.openstack.org/fuel-docs/latest/plugindocs/fuel-plugin-sdk-guide.html On Tue, May 1, 2018 at 3:42 PM, Jim Okken <j...@jokken.com> wrote: > hi Jitendra, > thanks very much for your reply! > > We deploy with the UI and right now the environment is set and we only add > compute nodes. > In the past we deployed one compute node at a time but now that we > understand the process we deploy multiple, 3 or 5 compute nodes at a time. > Honestly though going fwd it could be 1 or multiple nodes at a time. > This is an growing internal-use environment, but we have 23 compute nodes > right now, so we are going to be growing it slower going fwd. > > Right now we have some simple shell scripts which we run after a > successful deploy, these set the settings in the config files and restart > openstack services. But until those scripts are run the environment is > missing those needed additions and not really usable. > Not a huge problem for an internal-use environment, but we would like to > have no downtime. > Also it is HA so we have 3 controllers. > > thanks!! > > > -- Jim > > On Tue, May 1, 2018 at 3:39 PM, Jitendra Kumar Bhaskar < > jitendr...@pramati.com> wrote: > >> Hi Jim, >> >> I can help you one that, but before that wanted to understand how are you >> deploying the additional computes: >> 1. If CLI then share the command that you used to deploy. >> 2. If UI then are you deploying only one node after selection ? >> >> >> Regards >> Jitendra Bhaskar >> >> Regards >> Bhaskar >> +1-469-514-7986 >> >> >> >> >> >> On Tue, May 1, 2018 at 12:21 PM, Jim Okken <j...@jokken.com> wrote: >> >>> Hi list, >>> >>> >>> >>> We’ve created a pretty large openstack Newton HA environment using fuel. >>> After initial hiccups with deployment (not all fuel troubles) we can now >>> add additional compute nodes to the environment with ease! >>> >>> Thank you for all who’ve worked on all the projects to make this product. >>> >>> >>> >>> My question has to do with something I think I should know already: How >>> can we get fuel to stop overwriting custom settings in our environment? >>> When we deploy new compute nodes, original openstack settings on all nodes >>> are re-deployed/re-set. >>> >>> >>> >>> For example we have changes to settings in these files on the controller >>> nodes. >>> >>> >>> >>> /etc/nova/nova.conf >>> >>> /etc/neutron/dhcp_agent.ini >>> >>> /etc/neutron/plugins/ml2/openvswitch_agent.ini >>> >>> /etc/openstack-dashboard/local_settings.py >>> >>> /etc/keystone/keystone.conf >>> >>> /etc/cinder/cinder.conf >>> >>> /etc/neutron/neutron.conf >>> >>> >>> >>> I’m guessing the method to resolve this is not to stop fuel from >>> overwriting settings, but to add to fuel some tasks that sets these custom >>> settings again near the end of each deploy. >>> >>> >>> >>> I’m sure this is something I am supposed to know already, but so far in >>> my route thru Openstack land experience with this has escaped me. >>> >>> Can you send me some advice, pointers, places to start? >>> >>> >>> >>> Thanks! >>> >>> >>> >>> --jim >>> >>> >>> _______________________________________________ >>> 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/listinfo/openstack >>> >>> >> >> Disclaimer: >> The contents of this email and any attachments are confidential. They are >> intended for the named recipient(s) only. If you have received this email >> by mistake, please notify the sender immediately and do not disclose the >> contents to anyone or make copies thereof. >> > > > _______________________________________________ > 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/listinfo/ > openstack > >
_______________________________________________ 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/listinfo/openstack
