Thanks John for the info. I am going through the spec in detail. And before that, I had few thoughts about how I wanted to approach this, which I have drafted in https://etherpad.openstack.org/p/tripleo-derive-params. And it is not 100% ready yet, I was still working on it.
As of now, there are few differences on top of my mind, which I want to highlight, I am still going through the specs in detail: * Profiles vs Features - Considering a overcloud node as a profiles rather than a node which can host these features, would have limitations to it. For example, if i need a Compute node to host both Ceph (OSD) and DPDK, then the node will have multiple profiles or we have to create a profile like - hci_enterprise_many_small_vms_with_dpdk? The first one is not appropriate and the later is not scaleable, may be something else in your mind? * Independent - The initial plan of this was to be independent execution, also can be added to deploy if needed. * Not to expose/duplicate parameters which are straight forward, for example tuned-profile name should be associated with feature internally, Workflows will decide it. * And another thing, which I couldn't get is, where will the workflow actions be defined, in THT or tripleo_common? The requirements which I thought of, for deriving workflow are: Parameter Deriving workflow should be * independent to run the workflow * take basic parameters inputs, for easy deployment, keep very minimal set of mandatory parameters, and rest as optional parameters * read introspection data from Ironic DB and Swift-stored blob I will add these comments as starting point on the spec. We will work towards bringing down the differences, so that operators headache is reduced to a greater extent. Regards, Saravanan KR On Fri, Jan 20, 2017 at 9:56 PM, John Fulton <johfu...@redhat.com> wrote: > On 01/11/2017 11:34 PM, Saravanan KR wrote: >> >> Thanks John, I would really appreciate if you could tag me on the >> reviews. I will do the same for mine too. > > > Hi Saravanan, > > Following up on this, have a look at the OS::Mistral::WorflowExecution > Heat spec [1] to trigger Mistral workflows. I'm hoping to use it for > deriving THT parameters for optimal resource isolation in HCI > deployments as I mentioned below. I have a spec [2] which describes > the derivation of the values, but this is provided as an example for > the more general problem of capturing the rules used to derive the > values so that deployers may easily apply them. > > Thanks, > John > > [1] OS::Mistral::WorflowExecution https://review.openstack.org/#/c/267770/ > [2] TripleO Performance Profiles https://review.openstack.org/#/c/423304/ > >> On Wed, Jan 11, 2017 at 8:03 PM, John Fulton <johfu...@redhat.com> wrote: >>> >>> On 01/11/2017 12:56 AM, Saravanan KR wrote: >>>> >>>> >>>> Thanks Emilien and Giulio for your valuable feedback. I will start >>>> working towards finalizing the workbook and the actions required. >>> >>> >>> >>> Saravanan, >>> >>> If you can add me to the review for your workbook, I'd appreciate it. I'm >>> trying to solve a similar problem, of computing THT params for HCI >>> deployments in order to isolate resources between CephOSDs and >>> NovaComputes, >>> and I was also looking to use a Mistral workflow. I'll add you to the >>> review >>> of any related work, if you don't mind. Your proposal to get NUMA info >>> into >>> Ironic [1] helps me there too. Hope to see you at the PTG. >>> >>> Thanks, >>> John >>> >>> [1] https://review.openstack.org/396147 >>> >>> >>>>> would you be able to join the PTG to help us with the session on the >>>>> overcloud settings optimization? >>>> >>>> >>>> I will come back on this, as I have not planned for it yet. If it >>>> works out, I will update the etherpad. >>>> >>>> Regards, >>>> Saravanan KR >>>> >>>> >>>> On Wed, Jan 11, 2017 at 5:10 AM, Giulio Fidente <gfide...@redhat.com> >>>> wrote: >>>>> >>>>> >>>>> On 01/04/2017 09:13 AM, Saravanan KR wrote: >>>>>> >>>>>> >>>>>> >>>>>> Hello, >>>>>> >>>>>> The aim of this mail is to ease the DPDK deployment with TripleO. I >>>>>> would like to see if the approach of deriving THT parameter based on >>>>>> introspection data, with a high level input would be feasible. >>>>>> >>>>>> Let me brief on the complexity of certain parameters, which are >>>>>> related to DPDK. Following parameters should be configured for a good >>>>>> performing DPDK cluster: >>>>>> * NeutronDpdkCoreList (puppet-vswitch) >>>>>> * ComputeHostCpusList (PreNetworkConfig [4], puppet-vswitch) (under >>>>>> review) >>>>>> * NovaVcpuPinset (puppet-nova) >>>>>> >>>>>> * NeutronDpdkSocketMemory (puppet-vswitch) >>>>>> * NeutronDpdkMemoryChannels (puppet-vswitch) >>>>>> * ComputeKernelArgs (PreNetworkConfig [4]) (under review) >>>>>> * Interface to bind DPDK driver (network config templates) >>>>>> >>>>>> The complexity of deciding some of these parameters is explained in >>>>>> the blog [1], where the CPUs has to be chosen in accordance with the >>>>>> NUMA node associated with the interface. We are working a spec [2], to >>>>>> collect the required details from the baremetal via the introspection. >>>>>> The proposal is to create mistral workbook and actions >>>>>> (tripleo-common), which will take minimal inputs and decide the actual >>>>>> value of parameters based on the introspection data. I have created >>>>>> simple workbook [3] with what I have in mind (not final, only >>>>>> wireframe). The expected output of this workflow is to return the list >>>>>> of inputs for "parameter_defaults", which will be used for the >>>>>> deployment. I would like to hear from the experts, if there is any >>>>>> drawbacks with this approach or any other better approach. >>>>> >>>>> >>>>> >>>>> >>>>> hi, I am not an expert, I think John (on CC) knows more but this looks >>>>> like >>>>> a good initial step to me. >>>>> >>>>> once we have the workbook in good shape, we could probably integrate it >>>>> in >>>>> the tripleo client/common to (optionally) trigger it before every >>>>> deployment >>>>> >>>>> would you be able to join the PTG to help us with the session on the >>>>> overcloud settings optimization? >>>>> >>>>> https://etherpad.openstack.org/p/tripleo-ptg-pike >>>>> -- >>>>> Giulio Fidente >>>>> GPG KEY: 08D733BA >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev