Hi Keong see comments in the mail
/Morgan Le mardi 09 juillet 2019 à 00:13 -0700, Keong Lim a écrit : > Hi Morgan, > > On Mon, Jul 8, 2019 at 03:47 PM, Morgan Richomme wrote: > > On our side we used to install incrementally ONAP using 4 steps > > - core (6): A&AI, DMAAP Message Router, Portal, SDC, SDNC, SO > > - small (9): core + AAF, APPC, CLI, External API, Log, MultiCloud, > > VID > > - medium (14): small + CLAMP, DCAE, Holmes, OOF, Policy, UseCase UI > > - full (61): all the components (VFC + all VFC drivers, VNFSDK, > > Modeling, > > Pomba, Multicloud drivers, Dmaap Bus controller, ...) > > Does the "install" phase for these pods actually result in the pods > starting up as well? yes installation + start > Or are the pods only started after everything has been "installed"? > > AAI depends on AAF during startup. > AAI-Resources deployment chart contains MSB configuration that needs > to be injected during startup. > So, AAF and MSB should be started before AAI, but neither of them > appears in the "core" list. you are right, my list was not correct, I reused the one from the healthcheck tests we made some changes due to the depenencies when we installed incrementally, we installed AAF and the common databases in core (even AAF healthcheck is in small) please note that we now install everything in // and do not do it incrementally. > For that matter, the common Cassandra should be in the "core" list > too. yes you are right, the common maria DB as well > > This installation sequence seems different from the proper startup > sequence. > > Doing these 4 steps appears to be explicitly countermanding the Helm > chart dependencies, i.e. the "initContainers" section of the > deployment.yaml files. > If the Helm chart dependencies are not properly expressed, then > tweaking some timers is not a guaranteed fix for other operators who > run ONAP in their environments. agree that is why we are now installating everything at once relying on helm chart dependencies. > > In the near future, the intention is for AAI pods to generate AAF > certificates on startup (as demonstrated in the aaf-hello pod), so > this particular sequence seems likely to fail again. > > > Keong _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17925): https://lists.onap.org/g/onap-discuss/message/17925 Mute This Topic: https://lists.onap.org/mt/32393410/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
