Hello guys, Could you provide feedback on this updated version of onap-parameters.yaml? https://gerrit.onap.org/r/#/c/28591/5/kubernetes/config/onap-parameters-sample.yaml
It’s under review, and I’d love a little but a feedback. I added a lot of comments explaining what are the param to give. Please let me know if it helps and does answer your questions. Thanks, Alexis > On Jan 18, 2018, at 12:59 PM, Alexis de Talhouët <[email protected]> > wrote: > > Gary, > > For now Amsterdam branch has been highly tested. I’m starting the work on the > master branch. > So please use Amsterdam branch for now. > > Regarding the issue you faced with the init container, this should be fix > now.You could try to re-pull the config-init:2.0.0-SNAPSHOT image (for master) > > The config container does provision directory, and it does also a bunch of > sed command to inject parameters, Those sed commands is what is taking most > of the time, because we loop blindly over all the directories, instead of > targeting the sed more precisely. I’m currently working on improving this for > Amsterdam, and will cherry-pick on master once ready. > > Thanks, > Alexis > >> On Jan 18, 2018, at 12:49 PM, Gary Wu <[email protected] >> <mailto:[email protected]>> wrote: >> >> Are we mainly testing against OOM amsterdam branch, or master? >> >> In the master branch, the config container complains about other parameters >> missing like NEXUS_REPO or something. Is the OOM master branch stable >> enough for us to try now? If so, can you share your sample parameters file >> for the master branch? >> >> As an aside, does anyone know why the config container takes 2 to 3 minutes >> to complete? Seems to be a long time for creating shared config >> directories, or maybe my environment is not set up right somehow. >> >> Thanks, >> Gary >> >> From: [email protected] >> <mailto:[email protected]> >> [mailto:[email protected] >> <mailto:[email protected]>] On Behalf Of Alexis de Talhouët >> Sent: Thursday, January 18, 2018 9:14 AM >> To: PLATANIA, MARCO (MARCO) <[email protected] >> <mailto:[email protected]>> >> Cc: onap-discuss <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod >> lab >> >> Marco, >> >> Well that’s the thing I’m currently looking at. I know Robot needs them for >> whatever reason. >> >> I’m currently about to test a deployment without those parameters, because >> as you pointed out, they don’t necessarily make sense for OOM. >> >> I have to validate this, but I’m validating other thing at the same time. >> Because with the introduction of DCAE, we potentially can configure tree >> different OpenStack: >> >> - 1 where to deploy VNF >> - 1 where to deploy DCAE >> - 1 where DNS Designate is supported >> >> So I’m re-doing the onap-parameters.yaml to take this in consideration. >> Note, it could also be the same OpenStack instance for all of them, but as >> the flexibility is giving to us >> by DCAE, let’s leverage this. >> >> Moreover, this separation is useful when going in prod. >> >> Alexis >> >> >> On Jan 18, 2018, at 12:06 PM, PLATANIA, MARCO (MARCO) >> <[email protected] <mailto:[email protected]>> wrote: >> >> Alexis, >> >> What are these parameters used for in OOM? >> >> OPENSTACK_UBUNTU_14_IMAGE: "ubuntu-14-04-cloud-amd64" >> OPENSTACK_PUBLIC_NET_ID: "971040b2-7059-49dc-b220-4fab50cb2ad4" >> OPENSTACK_OAM_NETWORK_ID: "31b5d82c-bfd3-44bf-a830-4bc0b628013f" >> OPENSTACK_OAM_SUBNET_ID: "658d0e1b-8e2c-45c3-94e3-e7a1df1ed475" >> OPENSTACK_OAM_NETWORK_CIDR: "10.10.2.0/24" >> >> We had them for Heat, to tell the Orchestrator what image and network to use >> when creating ONAP VMs. For vFW/vLB use cases, those parameters are passed >> as SDNC preload. >> >> Marco >> >> From: <[email protected] >> <mailto:[email protected]>> on behalf of Alexis de >> Talhouët <[email protected] <mailto:[email protected]>> >> Date: Thursday, January 18, 2018 at 11:47 AM >> To: Pavel Paroulek <[email protected] <mailto:[email protected]>> >> Cc: onap-discuss <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod >> lab >> >> Hi, >> >> I don’t know which tenant you’re using, but for the OOM tenant, here is my >> onap-parameters.yaml file. >> >> Note: this was my parameters two months ago, I do not guarantee the values >> are still accurate. >> >> # Look at the images >> OPENSTACK_UBUNTU_14_IMAGE: "ubuntu-14-04-cloud-amd64" >> # Look at the networks >> OPENSTACK_PUBLIC_NET_ID: "971040b2-7059-49dc-b220-4fab50cb2ad4" >> OPENSTACK_OAM_NETWORK_ID: "31b5d82c-bfd3-44bf-a830-4bc0b628013f" >> OPENSTACK_OAM_SUBNET_ID: "658d0e1b-8e2c-45c3-94e3-e7a1df1ed475" >> OPENSTACK_OAM_NETWORK_CIDR: "10.10.2.0/24" >> # your credentials >> OPENSTACK_USERNAME: “YOUR_USER" >> OPENSTACK_API_KEY: “YOUR_PASSWORD" >> # the tenant to use, the name and id >> OPENSTACK_TENANT_NAME: "OOM" >> OPENSTACK_TENANT_ID: "dbe658c72ee7426fa979e319fd8cacc7" >> # the cloud region, usually RegionOne for OpenStack >> OPENSTACK_REGION: “RegionOne" >> # keystone URL >> OPENSTACK_KEYSTONE_URL: "http://10.12.25.2:5000 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.12.25.2-3A5000&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=P30mexfy2QtZzF7TJbV-bBD__vyMnWre376ngo3OcR4&s=0CFvSpWFDKqJm9p089ICYZeVCVzHIOJtYGirkajpt3M&e=>" >> # Look at the flavor >> OPENSTACK_FLAVOUR_MEDIUM: "m1.medium” >> # Let them as is >> OPENSTACK_SERVICE_TENANT_NAME: "service" >> DMAAP_TOPIC: "AUTO" >> DEMO_ARTIFACTS_VERSION: “1.1.1" >> >> Thanks, >> Alexis >> >> >> >> On Jan 18, 2018, at 11:41 AM, Pavel Paroulek <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Alexis, >> >> does it make sense to provide sample values (in the sample config file) for >> the winriver pod lab or a description how to obtain them? For example I am >> not allowed (403) to read the openstack services so I am not sure how to get >> the service tenant name (maybe I am using the wrong command). It would also >> be interesting to know what subset of these config keys is mandatory (if >> any) and which are optional. >> >> Br, >> Pavel >> >> >> ---- On Thu, 18 Jan 2018 17:28:57 +0100 Alexis de >> Talhouët<[email protected] <mailto:[email protected]>> wrote ---- >> >> Hello, >> >> The onap-parameters.yaml file have significantly changed on Amsterdam, since >> the work to get DCAE deployed by OOM has been merged. >> >> I’m currently re-working this file, to first: add explanation for every >> parameters, and second, to make it more modulable. >> >> I’ll circle back on this mail thread once my work is done and merge. Also, I >> will update the OOM documentation. >> >> Thanks, >> Alexis >> >> On Jan 17, 2018, at 10:15 AM, Bainbridge, David <[email protected] >> <mailto:[email protected]>> wrote: >> >> While far from an expert, I have inserted where I have found the values in >> bold. To be honest, we haven’t got it working, but this seems a heat issue >> at this point for us. We are actually using devstack + heat for our pod. >> >> Avèk respè, >> /david >> >> anyone tried to configure OOM/k8s in the pod lab? The following options need >> to be configured: >> OPENSTACK_UBUNTU_14_IMAGE: "Ubuntu_14.04.5_LTS" >> You have to import an Ubuntu cloud image into OS. This is the name you give >> that image when you import it. >> >> OPENSTACK_PUBLIC_NET_ID: "971040b2-7059-49dc-b220-4fab50cb2ad4" >> This is the UUID of the public network that has been created in OS to use >> with the VNFs >> >> OPENSTACK_OAM_NETWORK_ID: "971040b2-7059-49dc-b220-4fab50cb2ad4" >> This is the UUID of the private network that has been created in OS to use >> with the VNFs >> >> OPENSTACK_OAM_SUBNET_ID: "7d2dd91b-08ac-463f-a292-91a1e1dd76d4" >> This is the UUID of the subnet of the private network that has been created >> in OS to with the VNFs >> >> OPENSTACK_OAM_NETWORK_CIDR: "10.12.25.0/16" >> This is the CIDR of the previously referenced subnet >> >> OPENSTACK_USERNAME: "OOM" >> OPENSTACK_API_KEY: "OOM" >> OPENSTACK_TENANT_NAME: "A & AI" >> OPENSTACK_TENANT_ID: "24f8eea7f8a146db9e6fa57aee8c3a1c" >> OPENSTACK_REGION: "RegionOne" >> OPENSTACK_KEYSTONE_URL: "http://10.12.25.2:5000/v3"; >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.12.25.2-3A5000_v3&d=DwMCaQ&c=06gGS5mmTNpWnXkc0ACHoA&r=rSscq0gxaY0raCkAEotD0QQEnyD5X2dD23irExAKUBI&m=dBndPBImU1OJD83-wiNeYoiwicIEU_uldtlXaRYTx10&s=8slFIY924DBO8DhhmaaURVhHSMClAvnvYV911ICnwVw&e=> >> OPENSTACK_FLAVOUR_MEDIUM: "m1.medium" >> OPENSTACK_SERVICE_TENANT_NAME: "service" >> This one I have always left as service. I assume it references a group or >> user. >> >> DMAAP_TOPIC: "AUTO" >> DEMO_ARTIFACTS_VERSION: "1.1.0-SNAPSHOT" >> I am not sure how to figure out the values for properties in bold. >> Anyone tried to get it working in the pod lab or knows how to get the >> correct values? >> Thanks, >> Pavel >> >> _______________________________________________ >> onap-discuss mailing list >> [email protected] <mailto:[email protected]> >> https://lists.onap.org/mailman/listinfo/onap-discuss >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=P30mexfy2QtZzF7TJbV-bBD__vyMnWre376ngo3OcR4&s=MJEFXDFsXY6CddXFAklt3eck8p5AWXmGvUcsaY33dDo&e=>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
