Re: [opnfv-tech-discuss] [fuel] Fuel/MCP virtual deployment failure due new redis 5.0 config file
Hi Martin, The Redis v5.0 package has been removed from repository recently, so we're going to switch back to 3.0 in reclass model, i.e. revert that patch. On Tue, Nov 13, 2018 at 3:44 PM Klozik Martin wrote: > Hi Michael, > > > after the merge of your patch below, I'm observing errors during Fuel/MCP > virtual installation at LAAS (labs.opnfv.org) servers. > > > https://gerrit.opnfv.org/gerrit/#/c/64871/ > > > The root cause is incompatible REDIS 5.0 configuration file, which is > being used for execution of REDIS 3.0 server, which is being deployed by > the installer. In case that I use commit before your merge, then > installation succeeds. > > > Steps to reproduce: > > 1) book hpe-xx machine at labs.opnfv.org > > 2) start VPN and ssh into hpe-xx > > 3) start virtual deployment: > > git clone https://gerrit.opnfv.org/gerrit/fuel > > cd fuel > > git checkout stable/gambia # 1st noticed at master branch, but stable is > also affected > > ci/deploy.sh -l ericsson -p virtual1 -s os-nosdn-nofeature-noha -D > > I'm not sure if only virtual deployment is affected, because I don't have > a HW POD to retest it. > > > Do you know, why redis 5.0 configuration file is applied, but redis > binaries were kept at version 3.0? > > > Thank you, > > Martin > -- Michael Polenchuk Private Cloud / Mirantis Inc. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22371): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22371 Mute This Topic: https://lists.opnfv.org/mt/28121837/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [Fuel] call for PTL elections
+1 On Tue, May 8, 2018 at 2:07 PM, Guillermo Herrero < guillermo.herr...@enea.com> wrote: > +1 > -- > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org < > opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of Greg Elkinbard < > elkin...@gmail.com> > *Sent:* Monday, May 7, 2018 8:22:22 PM > *To:* TECH-DISCUSS OPNFV > *Subject:* [opnfv-tech-discuss] [Fuel] call for PTL elections > > Hi folks, > As many of you remember, I have stepped down as Fuel PTL, but we have > never had an election to appoint a new one. Time to correct this issue. > > > We need to elect a new Fuel PTL. > Any active project committer is allowed to run. > > However I would like to nominate Alexandru Avadanii for his extra > ordinary contributions to the project over the last several years. > > Voting period is open for one week. Project committers are allowed to vote. > Committers please respond with the name of the candidate for PTL you > support. > > Thanks > Greg > > > > > This message, including attachments, is CONFIDENTIAL. It may also be > privileged or otherwise protected by law. If you received this email by > mistake please let us know by reply and then delete it from your system; > you should not copy it or disclose its contents to anyone. All messages > sent to and from Enea may be monitored to ensure compliance with internal > policies and to protect our business. Emails are not secure and cannot be > guaranteed to be error free as they can be intercepted, a mended, lost or > destroyed, or contain viruses. The sender therefore does not accept > liability for any errors or omissions in the contents of this message, > which arise as a result of email transmission. Anyone who communicates with > us by email accepts these risks. > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] Problems with MCP virtual deploy - stable/euphrates
Joe, let's go to the IRC (#opnfv-fuel) to debug it further ... On Fri, Mar 16, 2018 at 8:37 PM, Joe Kidder <joe.kid...@5thlayer.com> wrote: > Michael, > First is the nova service-list. > Second, thanks for the defect pointer - I have some further info - it > seems that this error about flavor not being found may be harmless…see > below… > Third, I have some comments/questions about how to fix original problem > of "No valid host was found.” > > *ubuntu@ctl01*:*~*$ nova service-list > ++--+---+--+-+-- > -++-+ > | Id | Binary | Host | Zone | Status | State | Updated_at > | Disabled Reason | > ++--+---+--+-+-- > -++-+ > | 3 | nova-scheduler | ctl01 | internal | enabled | up| > 2018-03-16T16:16:12.00 | - | > | 4 | nova-consoleauth | ctl01 | internal | enabled | up| > 2018-03-16T16:16:10.00 | - | > | 5 | nova-conductor | ctl01 | internal | enabled | up| > 2018-03-16T16:16:12.00 | - | > | 6 | nova-cert| ctl01 | internal | enabled | up| > 2018-03-16T16:16:16.00 | - | > | 7 | nova-compute | cmp01 | nova | enabled | up| > 2018-03-16T16:15:29.00 | - | > | 8 | nova-compute | cmp02 | nova | enabled | up| > 2018-03-16T16:15:40.00 | - | > ++--+---+--+-+-- > -++-+ > > I looked at the comments, and some of the error descriptions… > One thing that looked interesting was “open stack show flavor > ”…which didn’t work for one person, but worked for me: > *ubuntu@ctl01*:*~*$ openstack flavor show small > ++--+ > | Field | Value| > ++--+ > | OS-FLV-DISABLED:disabled | False| > | OS-FLV-EXT-DATA:ephemeral | 0| > | access_project_ids | None | > | disk | 10 | > | id | f3eca419-5939-4a55-a00b-53b796978a11 | > | name | small| > | os-flavor-access:is_public | True | > | properties | | > | ram| 1024 | > | rxtx_factor| 1.0 | > | swap | | > | vcpus | 1| > ++--+ > > But yes, there’s an exception in there, even though the command succeeded > as far as I could tell. > So perhaps *this flavor not found* is an red-herring - not the real > problem. Note - I now see that this shows up all over my other working > system’s nova-api.log files. > > Back to the original error, then, which is "No valid host was found. > There are not enough hosts available” > > I’m hitting this problem whether I launch via heat and a heat template > (that works on my arm bare-metal pod, by the way, substituting the correct > architecture > I can dig some more - either on my own (maybe efficient, maybe not;) - or > perhaps this failure is interesting enough to debug… > > The interesting question is whether the stable/euphrates virtual deploy > with MCP/Fuel *should *work or whether there is an issue (like some > update broke stable/E branch?). > OR whether it’s something to do with my deployment (see original message > for command line of deploy) or lack of proper preparation for the server on > which I’m running. > > Also - let me know if you want to take this offline or retire to an IRC of > your choice. > And Lastly: I tried this with Master and hit some other issues that I > can’t remember, and thought master might be too risky - I just want a > virtual pod that I can run with, so either stable/E or master is good. > > My point of the last comment is that if you’d prefer I join you in > chasing/debugging/trying things in Master (towards Fraser) than me asking > you for advice with Stable/E, I’m certainly open to that:) > > Thanks much! > Joe > > On Mar 16, 2018, at 11:37 AM, Michael Polenchuk <mpolenc...@mirantis.com> > wrote: > > Pl
Re: [opnfv-tech-discuss] Problems with MCP virtual deploy - stable/euphrates
Please refer to the last comments of https://bugs.launchpad.net/nova/+bug/1558503 Could you please show "nova service-list" output? On Fri, Mar 16, 2018 at 7:27 PM, Joe Kidder <joe.kid...@5thlayer.com> wrote: > For at least one of the flavors, I also tried providing the flavor ID > rather than the flavor name. Same error. > > On Mar 16, 2018, at 11:16 AM, Joe Kidder <joe.kid...@5thlayer.com> wrote: > > I did add the flavors that I used. > They exist prior to trying to use them. > > *ubuntu@ctl01*:*~*$ openstack flavor list > +--+---+--+- > -+---+---+---+ > | ID | Name | RAM | Disk | > Ephemeral | VCPUs | Is Public | > +--+---+--+- > -+---+---+---+ > | 056f9f85-4b09-4813-a7f6-648f1b1443e5 | medium| 4096 | 20 | > 0 | 2 | True | > | 87113070-c6ac-4801-b447-0308c2adb3b2 | m1.medium | 4096 | 40 | > 0 | 2 | True | > | f3eca419-5939-4a55-a00b-53b796978a11 | small | 1024 | 10 | > 0 | 1 | True | > +--+---+--+- > -+---+---+---+ > > Trying all three of the above flavors all led to the same thing: > 2018-03-15 15:01:16.710 2219 INFO nova.api.openstack.wsgi > [req-10337a28-806b-4fb4-80ed-6798b0dd873a ea2fe03e3a32430caf82d2cbad9ee117 > 372d6563febd413aba9f407c0ef62eb1 - default default] HTTP exception > thrown: Flavor small could not be found. > > …just replace “small” with “medium” and with “m1.medium” > > Joe > > On Mar 16, 2018, at 4:22 AM, Michael Polenchuk <mpolenc...@mirantis.com> > wrote: > > Hi Joe, > > MCP doesn't add any flavors by default, please do it explicitly. > Also check out you have enough compute resources (e.g. cpu, memory, disk). > > On Thu, Mar 15, 2018 at 7:03 PM, Joe Kidder <joe.kid...@5thlayer.com> > wrote: > >> Hi, >> I am deploying OPNFV on an x86 server. >> I’m using stable Euphrates: >> git clone -b stable/euphrates https://github.com/opnfv/fuel >> >> I deploy like this: >> ci/deploy.sh -l UNH-LaaS -p virtual_auto2 -s os-nosdn-nofeature-noha |& >> tee deploy.log >> >> The install succeeds. >> >> However, when I try to launch a VM using a simple heat template (that >> works on a bare metal MCP installation of stable/euphrates), I get this >> from heat: >> ERROR due to "Message: No valid host was found. There are not enough >> hosts available., Code: 500” >> >> And this from nova-api.log: >> HTTP exception thrown: Flavor m1.medium could not be found. >> >> I tried this with three separate flavors, none of which could be found. >> >> Any thoughts? >> >> Thanks, >> Joe >> >> >> ___ >> opnfv-tech-discuss mailing list >> opnfv-tech-discuss@lists.opnfv.org >> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >> >> > > > -- > Michael Polenchuk > Private Cloud / Mirantis Inc. > > > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] Problems with MCP virtual deploy - stable/euphrates
Hi Joe, MCP doesn't add any flavors by default, please do it explicitly. Also check out you have enough compute resources (e.g. cpu, memory, disk). On Thu, Mar 15, 2018 at 7:03 PM, Joe Kidder <joe.kid...@5thlayer.com> wrote: > Hi, > I am deploying OPNFV on an x86 server. > I’m using stable Euphrates: > git clone -b stable/euphrates https://github.com/opnfv/fuel > > I deploy like this: > ci/deploy.sh -l UNH-LaaS -p virtual_auto2 -s os-nosdn-nofeature-noha |& > tee deploy.log > > The install succeeds. > > However, when I try to launch a VM using a simple heat template (that > works on a bare metal MCP installation of stable/euphrates), I get this > from heat: > ERROR due to "Message: No valid host was found. There are not enough hosts > available., Code: 500” > > And this from nova-api.log: > HTTP exception thrown: Flavor m1.medium could not be found. > > I tried this with three separate flavors, none of which could be found. > > Any thoughts? > > Thanks, > Joe > > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [fuel] Nominating Guillermo Herrero as committer
+1 On Thu, Jan 11, 2018 at 5:15 AM, Alexandru Avadanii < alexandru.avada...@enea.com> wrote: > Hi, > > I would like to nominate Guillermo Herrero (Enea) as a committer in > Fuel@OPNFV. > > I have been in contact with Guillermo and he is willing to take on the > role. > > > > Guillermo is one of the main contributors in Armband and Fuel@OPNFV, > > and he has been one of the most active and valuable contributors during > the Euphrates release cycle. > > > > Fuel committers, reply to this mail with your vote (-1, 0, +1). > > I’ll start: > > +1 > > > > BR, > > Alex > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] 答复: [opnfv-tsc] [release] Intent to Participate in "F" Release
Hi, The Fuel@OPNFV project intends to participate in the OPNFV Fraser release. > Today marks the opening of the intent-to-participate window for the "F" > release (i.e. MS0). Please find the procedure here > <https://wiki.opnfv.org/display/DEV/Project+Inclusion+in+OPNFV+Release>. > The window closes as of MS1 on Nov 3. > > > > > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] Error fuel deployment in all versions
Hi,
Could you please get the latest Fuel Danube iso?
Also please check out the disk free space on fuel master.
On Tue, Jul 25, 2017 at 10:26 PM, Ishpreet Kaur <ikaur...@uottawa.ca> wrote:
>
> Hi team,
>>
>> As in earlier message i told you about an error during fuel(brahmputra)
>> version , but today i try to deploy colorado1.0 version and getting the
>> same error at provisiong
>>
>> i am enclosing the error report, i hope you can help me please, as it is
>> a last of my deployment please
>> i shall be really thankful to you.
>>
>>
>> here an error during provisioning of nodes:
>>
>> Provision has failed. Failed to execute hook 'shell' Failed to run
>> command cd / && fa_build_image --image_build_dir /var/lib/fuel/ibp
>> --log-file /var/log/fuel-agent-env-2.log --data_driver nailgun_build_image
>> --input_data '{"image_data": {"/boot": {"container": "gzip", "uri": "
>> http://10.20.0.2:8080/targetimages/env_2_ubuntu_1404_amd64-boot.img.gz;,
>> "format": "ext2"}, "/": {"container": "gzip", "uri": "
>> http://10.20.0.2:8080/targetimages/env_2_ubuntu_1404_amd64.img.gz;,
>> "format": "ext4"}}, "output": "/var/www/nailgun/targetimages", "repos":
>> [{"name": "ubuntu", "section": "main multiverse restricted universe",
>> "uri": "http://10.20.0.2:8080/mirrors/ubuntu;, "priority": null,
>> "suite": "trusty", "type": "deb"}, {"name": "ubuntu-updates", "section":
>> "main multiverse restricted universe", "uri": "http://10.20.0.2:8080/
>> mirrors/ubuntu", "priority": null, "suite": "trusty-updates", "type":
>> "deb"}, {"name": "ubuntu-security", "section": "main multiverse restricted
>> universe", "uri": "http://10.20.0.2:8080/mirrors/ubuntu;, "priority":
>> null, "suite": "trusty-security", "type": "deb"}], "packages": ["acl",
>> "anacron", "bash-completion", "bridge-utils", "bsdmainutils",
>> "build-essential", "cloud-init", "curl", "daemonize", "debconf-utils",
>> "gdisk", "grub-pc", "hpsa-dkms", "hwloc", "i40e-dkms", "linux-firmware",
>> "linux-firmware-nonfree", "linux-headers-generic-lts-trusty",
>> "linux-image-generic-lts-trusty", "lvm2", "mcollective", "mdadm",
>> "multipath-tools", "multipath-tools-boot", "nailgun-agent",
>> "nailgun-mcagents", "network-checker", "ntp", "openssh-client",
>> "openssh-server", "puppet", "python-amqp", "ruby-augeas", "ruby-ipaddress",
>> "ruby-json", "ruby-netaddr", "ruby-openstack", "ruby-shadow", "ruby-stomp",
>> "telnet", "ubuntu-minimal", "ubuntu-standard", "uuid-runtime", "vim",
>> "virt-what", "vlan"], "codename": "trusty"}' (node master returned 255).
>>
>>
>> I will really appreciate if anyone can help me.
>>
>> Regards
>> Ishpreet kaur
>> Uottawa
>>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
--
Michael Polenchuk
Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [release][euphrates] Milestone 3.2 - installers deploy scenario with integrated SDN and pass health check
Hi, There are the results for Fuel/MCP: https://build.opnfv.org/ci/job/functest-fuel-virtual-daily-master/1941/console Health check passed for os-odl_l2-nofeature-noha scenario. On Mon, Jul 10, 2017 at 7:49 PM, David McBride <dmcbr...@linuxfoundation.org > wrote: > Installer teams, > > Milestone 3.2 is scheduled for tomorrow, July 11. Please provide the > following: > >- Identify a scenario that includes an integrated SDN controller that >demonstrates that your installer meets the requirements of MS3.2. >- Provide a pointer to test results that demonstrate that health check >passes for the identified scenario. > > David > > -- > *David McBride* > Release Manager, OPNFV > Mobile: +1.805.276.8018 > Email/Google Talk: dmcbr...@linuxfoundation.org > Skype: davidjmcbride1 > IRC: dmcbride > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [fuel][plugins][odl] HA for ODL Controller in OpenStack
Hi, Fuel ODL plugin supports only one odl controller. ODL driver could be opted via UI settings of plugin. There are no plans to continue developing of this plugin but ... HA feature will be in MCP/Ocata soon. On Sun, Jun 25, 2017 at 2:36 PM, Raúl Alvarez Pinilla < ralva...@walhalladcs.com> wrote: > Hi all, > > I am testing OpenDaylight Plugin with Fuel 10.0 (Newton) and I have > noticed that you cannot create several ODL controllers in the same > environment, only it is possible to create only one ODL controller. > > Currently, with this plugin version, which version of ODL Driver is it > used? v1? v2? I am asking this because it seems that with v2 you can handle > several ODL controllers with HAProxy, am I right? Is there technical > documentation to deploy manually this feature? > > I would like to know if it is planned to continue developing this plugin > with OpenStack Ocata and resolve this HA limitation. With other installer > (Compass, TripleO, Juju) this feature is available? > > Thank you very much. > > Best regards, > [image: logowalhalladcs] > *Raúl Álvarez Pinilla* > > ralva...@walhalladcs.com www.walhalladcs.com > > -- > *Nota Legal*: Este correo electronico puede contener informacion > estrictamente confidencial y es de uso exclusivo del destinatario, quedando > prohibida a cualquier otra persona su revelacion, copia, distribucion, o el > ejercicio de cualquier accion relativa a su contenido. Si ha recibido este > correo electronico por error, por favor, conteste al remitente, y > posteriormente proceda a borrarlo de su sistema. Gracias por su > colaboracion. > > *Confidentiality notice*: This e-mail message may contain confidential > and/or legally privileged information and is solely for the attention and > use of the intended recipient. Any disclosure, copying, distribution or the > taking of any action with relation to the contents of this e-mail by any > other person is strictly prohibited. If you believe that this e-mail has > been mistakenly sent to you, please reply to the sender from whom you > received the message in error and then delete the original e-mail from your > system. Thank you for your co-operation. > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] Yardstick run-time issue
Hi, Yardstick team please have a look at https://build.opnfv.org/ci/job/yardstick-fuel-virtual-daily-master/1267/console RuntimeError: bash: iperf3: command not found RuntimeError: sudo: unable to resolve host fio: Connection timed out fio.sh: line 30: fio: command not found Thanks in advance. -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [Fuel] FUEL Deployment Error
Hi SarojX, In order to get it fixed in upstream, could you please file a bug (with logs/details) at https://bugs.launchpad.net/fuel/+filebug ? On Fri, Mar 17, 2017 at 2:24 AM, Serg Melikyan <smelik...@mirantis.com> wrote: > Hi SarojX, > > unfortunately I don't know what caused this issue. I've added mailing-list > to cc, in case community can help. > > On Thu, Mar 16, 2017 at 3:21 PM, Panigrahy, SarojX < > sarojx.panigr...@intel.com> wrote: > >> Hi Serg, >> >> >> >> Hope you are doing good. >> >> >> >> We are facing an error during deployment of network by using latest FUEL >> ISO(opnfv-2017-03-16_12-14-12.iso). >> >> >> >> *Error* >> Method task_deploy. Task[move_to_bootstrap/2]: Invalid task status! >> (#). >> Inspect Astute logs for the details >> >> >> >> Last few days, wehave faced this error in my set up. Previously, >> deployment is success in the same set up. >> >> FUEL ISO used- opnfv-2017-03-16_12-14-12.iso >> >> Fuel installation and setup creation has done successfully. During >> deployment through FUEL GUI, we face the above error. >> >> After discussing in #opnfv-fuel channel with AlexAvadanii, manually >> deployed the environment in fuel master and deployment >> done successfully. >> >> >> >> Request you to please check the issue and do needful to run deploy >> command from FUEL GUI. >> >> >> >> Thanks, >> >> Saroj >> >> >> > > > > -- > Serg Melikyan, Customer Success Manager at Mirantis, Inc. > http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979 > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation
Hi Anton, + Manuel I believe Manuel has more experience with SFC than me. On Wed, Mar 15, 2017 at 10:09 AM, Chivkunov, Anton <achiv...@mera.ru> wrote: > Hi Michael. > > > > If I didn’t cross the limit yet, I want to ask one more question about > PlugIn J > > On SFC main page (https://wiki.opendaylight.org > /view/Service_Function_Chaining:Main) there are several Demos available. > Demos 101&102 describe procedure of SFs/SFFs/Classifiers creation ( > https://drive.google.com/file/d/0BzS_qWNqsnQbUnEzU3BqVzdueTQ/view). > > There mentioned that SFC agent have to be started on corresponding node > for this purpose. To start SFC agent there is special script > “start_agent.sh”. But in our installation, with ODL/SFC as Plugin, we have > no this script available. I’m wondering if we need just to load this script > from SFC repo and use it, or there is another method for > SFs/SFFs/Classifiers creation provided in environments, deployed by Fuel, > and we should use some other way to create SFs/SFFs/Classifiers? > > > > *Not 100% sure that this question is really related to plugin. If it is > not, then please sorry for this. > > > > BR/Anton. > > > > *From:* Chivkunov, Anton > *Sent:* Friday, March 03, 2017 11:20 AM > *To:* 'Michael Polenchuk' > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* RE: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements > for ODL Controller with SFC. > > > > Hi Michael. > > > > Thank you for advice! > > Currently we are trying to use our most powerful node (16Gb of RAM and > 4-cores CPU) for Openstack + ODL Controller. Also we requested additional > RAM for all 5 nodes, to have 16-32Gb on each. > > If it will not help we also will try with dedicated node for ODL > controller as you suggested. > > > > BR/Anton. > > > > *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com > <mpolenc...@mirantis.com>] > *Sent:* Friday, March 03, 2017 11:10 AM > *To:* Chivkunov, Anton > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* Re: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements > for ODL Controller with SFC. > > > > Hi Anton, > > Definitely the timeout and low performance caused by RAM capacity. I guess > you have a lot of processes in swap. > > I would recommend to dedicate one node to opendaylight controller since > 8Gb is actually ain't enough for openstack+odl. > > Also for the openstack controllers itself the minimum/required RAM is > ~10-11Gb. > > > > On Thu, Mar 2, 2017 at 2:33 PM, Chivkunov, Anton <achiv...@mera.ru> wrote: > > Hi all. > > > > Sorry to bother you again, but we want to consult regarding HW > requirements for Controller node, which act as ODL controller as well. > > As it was described in initial mail, we have an environment, which consist > of Fuel master node, 3 Controller and 2 compute nodes. > > Controller nodes have 2-core Intel(R) Core(TM) i3-2100 CPUs. Two out of 3 > controllers have 8Gb of RAM, and one – 6 (not 16)Gb. ODL controller is one > of 8Gb nodes. > > > > Compute nodes have 16Gb RAM and next CPUs: > > Intel(R) Core(TM) i5-4460 CPU > > Intel(R) Core(TM) i3 CPU > > > > First of all, quite often during deployments in this configuration one or > few nodes can go away and back online: > Node 'Controller1 n103262' is back online > > Node 'Controller1 n103262' has gone away > > > > After such attempts part of functions are not operational and many tests > fails. > > When we are lucky and nodes were not away during deploy, most part of > tests works, only few of them may fail due to timeouts and work only after > several re-runs. > > At this step we are able to create/ping instances and so on, but as soon > as we install SFC UI and try do to something there everything breaks: > > - Existing instances are not pingable > > - New instances can’t be created due to error from > nova-scheduler (no hosts found) > > - CPU load on ODL controller becomes extremely high (up to > 100%) and even Controller restart doesn’t help > > - ODL controller goes away and back online in fuel time to time > > - SFC UI very-very slow > > > > I’m wondering if all these problems are due to low performance of our > node? In presentation from Luis Gomez I fount next table with requirements > and we are above minimum values: > > > > But I guess it might be for configurations without OpenStack and when ODL > work as PlugIn for Fuel/Openstack requirements should be higher? > > For example on http://artifacts.opnfv.org/pharos/docs/pharos-spec.html I > se
Re: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements for ODL Controller with SFC.
Hi Anton, Definitely the timeout and low performance caused by RAM capacity. I guess you have a lot of processes in swap. I would recommend to dedicate one node to opendaylight controller since 8Gb is actually ain't enough for openstack+odl. Also for the openstack controllers itself the minimum/required RAM is ~10-11Gb. On Thu, Mar 2, 2017 at 2:33 PM, Chivkunov, Anton <achiv...@mera.ru> wrote: > Hi all. > > > > Sorry to bother you again, but we want to consult regarding HW > requirements for Controller node, which act as ODL controller as well. > > As it was described in initial mail, we have an environment, which consist > of Fuel master node, 3 Controller and 2 compute nodes. > > Controller nodes have 2-core Intel(R) Core(TM) i3-2100 CPUs. Two out of 3 > controllers have 8Gb of RAM, and one – 6 (not 16)Gb. ODL controller is one > of 8Gb nodes. > > > > Compute nodes have 16Gb RAM and next CPUs: > > Intel(R) Core(TM) i5-4460 CPU > > Intel(R) Core(TM) i3 CPU > > > > First of all, quite often during deployments in this configuration one or > few nodes can go away and back online: > Node 'Controller1 n103262' is back online > > Node 'Controller1 n103262' has gone away > > > > After such attempts part of functions are not operational and many tests > fails. > > When we are lucky and nodes were not away during deploy, most part of > tests works, only few of them may fail due to timeouts and work only after > several re-runs. > > At this step we are able to create/ping instances and so on, but as soon > as we install SFC UI and try do to something there everything breaks: > > - Existing instances are not pingable > > - New instances can’t be created due to error from > nova-scheduler (no hosts found) > > - CPU load on ODL controller becomes extremely high (up to > 100%) and even Controller restart doesn’t help > > - ODL controller goes away and back online in fuel time to time > > - SFC UI very-very slow > > > > I’m wondering if all these problems are due to low performance of our > node? In presentation from Luis Gomez I fount next table with requirements > and we are above minimum values: > > > > But I guess it might be for configurations without OpenStack and when ODL > work as PlugIn for Fuel/Openstack requirements should be higher? > > For example on http://artifacts.opnfv.org/pharos/docs/pharos-spec.html I > see that 32Gb and Intel Xeon E5-2600v2 Series (Ivy Bridge and newer, or > similar) are mentioned. > > > > Could you please confirm if our problems are really due to too low > performance of HW and if so, then which characteristics are recommended? > > > > Thank you in advance! > > BR/Anton. > > > > *From:* Chivkunov, Anton > *Sent:* Monday, February 20, 2017 11:28 AM > *To:* 'Michael Polenchuk' > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* RE: [opnfv-tech-discuss] [fuel][plugins][odl] SFC UI > > > > Hi Michael. > > > > Ok, clear, thank you for clarifications! > > I’m really happy that we were able to get UI after installing > “feature:install odl-sfc-ui”, proposed by Pau. > > > > Thanks to both of you for quick response! > > > > BR/Anton. > > > > > > *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com > <mpolenc...@mirantis.com>] > *Sent:* Monday, February 20, 2017 10:51 AM > *To:* Chivkunov, Anton > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC UI > > > > Hi Anton, > > The patch is on review: > https://review.openstack.org/435878 > > > > On Fri, Feb 17, 2017 at 3:06 PM, Chivkunov, Anton <achiv...@mera.ru> > wrote: > > Just want to modify subject. > > > > *From:* Chivkunov, Anton > *Sent:* Friday, February 17, 2017 1:53 PM > *To:* 'opnfv-tech-discuss@lists.opnfv.org' > *Subject:* [fuel][plugins][odl] > > > > Hi Experts! > > > > We have an environment, which consist of 3 Controller and 2 compute nodes, > where we would like to try SFC. > > Deployment was done using Fuel, with OpenDaylight (with SFC features) and > Openvswitch plugins installed. But after deployment in OpenDaylight DLUX > user interface we don’t have anything related to SFC. It refer us to page > like this (not …/sfc/index.html): > > > > When we try to open http://192.168.203.210:8181/*sfc/*index.htm > <http://192.168.203.210:8181/sfc/index.htm> manually, we getting error > (no such page) > > > > When I go to OpenDaylight shell on controller node, I see in the list of > installed features that next SFC-
Re: [opnfv-tech-discuss] [SFC] Collecting current issues
Hi George, Thanks for the patch https://gerrit.opnfv.org/gerrit/29341 now healthcheck/dhcp_check works. On Thu, Feb 23, 2017 at 2:56 PM, Paraskevopoulos Georgios < geo...@intracom-telecom.com> wrote: > Hi all, > > > > I want to bring this back to life. In CI healtcheck is failing for SFC > scenario because the instances fail to get an IP from DHCP agent [0] > > In contrast for the BGPVPN scenario healthcheck works [1]. It seems to me > they are running a different flavor of healthcheck > > > > Michael: Is there any progress for this? Can we help to resolve this issue > somehow? > > > > [0] https://build.opnfv.org/ci/view/functest/job/functest- > fuel-baremetal-daily-master/1159/console > > [1] https://build.opnfv.org/ci/view/functest/job/functest- > fuel-baremetal-daily-master/1136/console > > > > BR, > > George > > > > > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: > opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Michael > Polenchuk > *Sent:* Thursday, February 16, 2017 2:58 PM > *To:* Jose Lausuch <jose.laus...@ericsson.com> > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* Re: [opnfv-tech-discuss] [SFC] Collecting current issues > > > > I've got only the following flows on the compute node (all instance(s) > packets is being dropped): > > # ovs-ofctl dump-flows -OOpenFlow13 br-int > OFPST_FLOW reply (OF1.3) (xid=0x2): > cookie=0x0, duration=36399.647s, table=0, n_packets=0, n_bytes=0, > dl_type=0x88cc actions=CONTROLLER:65535 > cookie=0x0, duration=36399.647s, table=0, n_packets=180, n_bytes=27686, > priority=6 actions=goto_table:1 > cookie=0x0, duration=36399.648s, table=1, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:11 > cookie=0x0, duration=36399.656s, table=11, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:21 > cookie=0x0, duration=36399.652s, table=21, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:31 > cookie=0x0, duration=36399.648s, table=31, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:41 > cookie=0x0, duration=36399.659s, table=41, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:51 > cookie=0x0, duration=36399.653s, table=51, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:61 > cookie=0x0, duration=36399.650s, table=61, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:71 > cookie=0x0, duration=36399.660s, table=71, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:81 > cookie=0x0, duration=36399.654s, table=81, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:91 > cookie=0x0, duration=36399.651s, table=91, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:101 > cookie=0x0, duration=36399.660s, table=101, n_packets=180, n_bytes=27686, > priority=0 actions=goto_table:111 > cookie=0x0, duration=36399.655s, table=111, n_packets=180, n_bytes=27686, > priority=0 actions=drop > > > > On Thu, Feb 16, 2017 at 12:53 PM, Michael Polenchuk < > mpolenc...@mirantis.com> wrote: > > Hi, > > Definitely need to debug it in details, > but I believe this issue relates to ovs+nsh chains/flows since other > scenarios pass this test. > > > > On Wed, Feb 15, 2017 at 10:10 PM, Jose Lausuch <jose.laus...@ericsson.com> > wrote: > > Hi, > > > > Currently there is a bigger problem which happens in CI: > > https://build.opnfv.org/ci/view/functest/job/functest- > fuel-baremetal-daily-master/1112/console > > > > The instances can’t get an IP from the dhcp agent. > > > > Adding Michail, who together with me has seen that issue before on fuel > and sometimes was due to bad POD configuration. > > > > Thanks, > > Jose > > > > > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: > opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Juan Vidal > ALLENDE > *Sent:* Wednesday, February 15, 2017 17:03 PM > *To:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* [opnfv-tech-discuss] [SFC] Collecting current issues > > > > Hello, > > > > As we talked in the weekly meeting, let's compile the current issues that > we are facing, and try to focus on fixing them to stabilize the test cases. > We can then add them to JIRA and assign them. > > > > I am currently facing two issues: > > > > 1) Floating IPs are not working sometimes. I don't know why this happens, > because manually I can spawn a VM and manually asign IP to it and works > fine with the admin user, but I seem to have more problems when using the > 'tacker' user. > > > > 2) Wait for ovs configurati
Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC UI
Hi Anton, The patch is on review: https://review.openstack.org/435878 On Fri, Feb 17, 2017 at 3:06 PM, Chivkunov, Anton <achiv...@mera.ru> wrote: > Just want to modify subject. > > > > *From:* Chivkunov, Anton > *Sent:* Friday, February 17, 2017 1:53 PM > *To:* 'opnfv-tech-discuss@lists.opnfv.org' > *Subject:* [fuel][plugins][odl] > > > > Hi Experts! > > > > We have an environment, which consist of 3 Controller and 2 compute nodes, > where we would like to try SFC. > > Deployment was done using Fuel, with OpenDaylight (with SFC features) and > Openvswitch plugins installed. But after deployment in OpenDaylight DLUX > user interface we don’t have anything related to SFC. It refer us to page > like this (not …/sfc/index.html): > > > > When we try to open http://192.168.203.210:8181/*sfc/*index.htm > <http://192.168.203.210:8181/sfc/index.htm> manually, we getting error > (no such page) > > > > When I go to OpenDaylight shell on controller node, I see in the list of > installed features that next SFC-related features are installed: > > opendaylight-user@root>feature:list -i | grep -i sfc > > odl-ovsdb-sfc-api | 1.3.0-Boron | > x | odl-ovsdb-sfc-1.3.0-Boron| OpenDaylight :: > ovsdb-sfc :: api > > odl-ovsdb-sfc | 1.3.0-Boron | > x | odl-ovsdb-sfc-1.3.0-Boron| OpenDaylight :: > ovsdb-sfc > > odl-ovsdb-sfc-rest | 1.3.0-Boron | > x | odl-ovsdb-sfc-1.3.0-Boron| OpenDaylight :: > ovsdb-sfc :: REST > > odl-sfc-model | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: sfc :: > Model > > odl-sfc-provider | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: sfc :: > Provider > > odl-sfc-provider-rest | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: sfc :: > Provider > > odl-sfc-ovs| 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: > OpenvSwitch > > odl-sfc-openflow-renderer | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: > sfc-openflow-renderer > > > > I’m wondering if we have to do some additional steps after Fuel deployment > with plugin to get SFC UI available? I was not able to find any instruction > for this part and supposed that OpenDaylight DLUX user interface will open > SFC UI. > > > > Thank you in advance! > > BR/Anton. > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [SFC] Collecting current issues
I've got only the following flows on the compute node (all instance(s) packets is being dropped): # ovs-ofctl dump-flows -OOpenFlow13 br-int OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x0, duration=36399.647s, table=0, n_packets=0, n_bytes=0, dl_type=0x88cc actions=CONTROLLER:65535 cookie=0x0, duration=36399.647s, table=0, n_packets=180, n_bytes=27686, priority=6 actions=goto_table:1 cookie=0x0, duration=36399.648s, table=1, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:11 cookie=0x0, duration=36399.656s, table=11, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:21 cookie=0x0, duration=36399.652s, table=21, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:31 cookie=0x0, duration=36399.648s, table=31, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:41 cookie=0x0, duration=36399.659s, table=41, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:51 cookie=0x0, duration=36399.653s, table=51, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:61 cookie=0x0, duration=36399.650s, table=61, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:71 cookie=0x0, duration=36399.660s, table=71, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:81 cookie=0x0, duration=36399.654s, table=81, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:91 cookie=0x0, duration=36399.651s, table=91, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:101 cookie=0x0, duration=36399.660s, table=101, n_packets=180, n_bytes=27686, priority=0 actions=goto_table:111 cookie=0x0, duration=36399.655s, table=111, n_packets=180, n_bytes=27686, priority=0 actions=drop On Thu, Feb 16, 2017 at 12:53 PM, Michael Polenchuk <mpolenc...@mirantis.com > wrote: > Hi, > > Definitely need to debug it in details, > but I believe this issue relates to ovs+nsh chains/flows since other > scenarios pass this test. > > On Wed, Feb 15, 2017 at 10:10 PM, Jose Lausuch <jose.laus...@ericsson.com> > wrote: > >> Hi, >> >> >> >> Currently there is a bigger problem which happens in CI: >> >> https://build.opnfv.org/ci/view/functest/job/functest-fuel- >> baremetal-daily-master/1112/console >> >> >> >> The instances can’t get an IP from the dhcp agent. >> >> >> >> Adding Michail, who together with me has seen that issue before on fuel >> and sometimes was due to bad POD configuration. >> >> >> >> Thanks, >> >> Jose >> >> >> >> >> >> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: >> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Juan Vidal >> ALLENDE >> *Sent:* Wednesday, February 15, 2017 17:03 PM >> *To:* opnfv-tech-discuss@lists.opnfv.org >> *Subject:* [opnfv-tech-discuss] [SFC] Collecting current issues >> >> >> >> Hello, >> >> >> >> As we talked in the weekly meeting, let's compile the current issues that >> we are facing, and try to focus on fixing them to stabilize the test cases. >> We can then add them to JIRA and assign them. >> >> >> >> I am currently facing two issues: >> >> >> >> 1) Floating IPs are not working sometimes. I don't know why this happens, >> because manually I can spawn a VM and manually asign IP to it and works >> fine with the admin user, but I seem to have more problems when using the >> 'tacker' user. >> >> >> >> 2) Wait for ovs configuration goes too fast. After testing 'ssh blocked' >> subtest, 'http works' subtest usually fails. I noticed that if I add a >> delay of 10 seconds after 'wait_for_configuration_changes' function, it >> works. Apparently it takes some time for the rules to be correctly >> installed. >> >> >> >> Are you guys seeing these bugs as well? Do you have some others? >> >> >> >> Regards, >> >> Juan >> > > > > -- > Michael Polenchuk > Private Cloud / Mirantis Inc. > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [SFC] Collecting current issues
Hi, Definitely need to debug it in details, but I believe this issue relates to ovs+nsh chains/flows since other scenarios pass this test. On Wed, Feb 15, 2017 at 10:10 PM, Jose Lausuch <jose.laus...@ericsson.com> wrote: > Hi, > > > > Currently there is a bigger problem which happens in CI: > > https://build.opnfv.org/ci/view/functest/job/functest- > fuel-baremetal-daily-master/1112/console > > > > The instances can’t get an IP from the dhcp agent. > > > > Adding Michail, who together with me has seen that issue before on fuel > and sometimes was due to bad POD configuration. > > > > Thanks, > > Jose > > > > > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: > opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Juan Vidal > ALLENDE > *Sent:* Wednesday, February 15, 2017 17:03 PM > *To:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* [opnfv-tech-discuss] [SFC] Collecting current issues > > > > Hello, > > > > As we talked in the weekly meeting, let's compile the current issues that > we are facing, and try to focus on fixing them to stabilize the test cases. > We can then add them to JIRA and assign them. > > > > I am currently facing two issues: > > > > 1) Floating IPs are not working sometimes. I don't know why this happens, > because manually I can spawn a VM and manually asign IP to it and works > fine with the admin user, but I seem to have more problems when using the > 'tacker' user. > > > > 2) Wait for ovs configuration goes too fast. After testing 'ssh blocked' > subtest, 'http works' subtest usually fails. I noticed that if I add a > delay of 10 seconds after 'wait_for_configuration_changes' function, it > works. Apparently it takes some time for the rules to be correctly > installed. > > > > Are you guys seeing these bugs as well? Do you have some others? > > > > Regards, > > Juan > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] Functest ODL-SFC
>>> >>> 2017-02-13 9:14 GMT+01:00 <morgan.richo...@orange.com>: >>> >>>> Hi Pau >>>> >>>> on which scenario/installer did you try to execute this test? >>>> according to the dependencies delcared by the SFC team for Colorado >>>> version (https://git.opnfv.org/functest/tree/ci/testcases.yaml?h=sta >>>> ble/colorado) >>>> odl-sfc has the following constraints >>>> >>>> name: odl-sfc >>>> criteria: 'status == "PASS"' >>>> blocking: false >>>> description: >- >>>> Test suite for odl-sfc to test two chains and two SFs >>>> dependencies: >>>> installer: 'fuel' >>>> scenario: 'odl_l2-sfc' >>>> >>>> >>>> >>>> It means that the test is applicable only for Fuel installer and for >>>> the specific scenarios including odl_l2-sfc (so in practice >>>> os-odl_l2-sfc-ha or os-odl_l2-sfc-noha) >>>> If your configuration is not compatible, you got the type of messages >>>> you reported >>>> >>>> Please note that for Danube, the constraints evolved and apex is now >>>> compatible (https://git.opnfv.org/functest/tree/functest/ci/testcases.y >>>> aml) >>>> >>>> dependencies: >>>> installer: '(apex)|(fuel)' >>>> scenario: 'odl_l2-sfc' >>>> >>>> >>>> /Morgan >>>> >>>> >>>> Le 13/02/2017 à 04:21, KA PDE a écrit : >>>> >>>> Hi, >>>> >>>> I was giving Functest a try and I'm getting the following error: >>>> >>>> /usr/local/lib/python2.7/dist-packages/pip/_vendor/requests/ >>>> packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true >>>> SSLContext object is not available. This prevents urllib3 from configuring >>>> SSL appropriately and may cause certain SSL connections to fail. You can >>>> upgrade to a newer version of Python to solve this. For more information, >>>> see https://urllib3.readthedocs.io/en/latest/security.html#insec >>>> ureplatformwarning. >>>> InsecurePlatformWarning >>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known >>>> hosts. >>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known >>>> hosts. >>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known >>>> hosts. >>>> Warning: Permanently added '10.20.0.5' (ECDSA) to the list of known >>>> hosts. >>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known >>>> hosts. >>>> 2017-02-13 03:15:28,500 - ODL_SFC - INFO - The presetup of the server >>>> worked >>>> 2017-02-13 03:15:28,689 - ODL_SFC - INFO - Executing ssh to collect the >>>> compute IPs >>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known >>>> hosts >>>> (...) >>>> Warning: Permanently added '10.20.0.6' (ECDSA) to the list of known >>>> hosts. >>>> 2017-02-13 03:15:37,096 - ODL_SFC - ERROR - Currently supported only >>>> Fuel Installer type >>>> >>>> ^^ >>>> >>>> Could someone provide any hint? >>>> >>>> Thanks and best regards, >>>> >>>> Pau >>>> >>>> >>>> ___ >>>> opnfv-tech-discuss mailing >>>> listopnfv-tech-discuss@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >>>> >>>> >>>> >>>> -- >>>> Morgan Richomme >>>> Orange/ IMT/ OLN/ CNC/ NCA/ SINA >>>> >>>> Network architect for innovative services >>>> Future of the Network community member >>>> Open source Orange community manager >>>> >>>> >>>> tel. +33 (0) 296 072 106 >>>> mob. +33 (0) 637 753 326morgan.richo...@orange.com >>>> >>>> _ >>>> >>>> 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. >>>> >>>> >>> >> > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing with br-aux not found
Hi George,
The private network is created by default, you just need to assign it to an
interface on each of the node.
Please look at the following docs:
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/configure-environment/map-logical-to-physical-nic.html
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/configure-environment/network-settings.html
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/sysreq/sysreq_network_requirements.html
Also if DPDK ain't requirement, please turn it off for now.
On Fri, Jan 27, 2017 at 7:54 PM, Paraskevopoulos Georgios <
geo...@intracom-telecom.com> wrote:
> Hi Michael,
>
>
>
> I think I found a possible cause for this issue
>
>
>
> From the dashboard I see that we don’t have a Private network.
>
> In the code I see:
>
> roles['neutron/private'] = 'br-aux' if orig_roles.key?('neutron/
> private')
>
>
>
> Perhaps this is the root cause that br-aux is missing? Can you guide me
> how to create a private network?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Paraskevopoulos
> Georgios
> *Sent:* Friday, January 27, 2017 5:39 PM
> *To:* Michael Polenchuk <mpolenc...@mirantis.com>
>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org;
> Veena Lingadahalli <vlingadaha...@mvista.com>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Ok I’ll wait a bit for a Fuel 10 patch.
>
>
>
> Thanks for your help,
>
> George
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com]
> *Sent:* Friday, January 27, 2017 5:34 PM
> *To:* Paraskevopoulos Georgios <geo...@intracom-telecom.com>
> *Cc:* Manuel Buil <mb...@suse.com>; opnfv-us...@lists.opnfv.org;
> opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli <
> vlingadaha...@mvista.com>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi George,
>
> This commit is intended only for 9.0 branch of odl plugin
>
> (i.e. for Fuel 9/mitaka).
>
>
>
> On Fri, Jan 27, 2017 at 7:23 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi Michael,
>
>
>
> There is only one file, astute.yaml
>
> Here are the contents: http://pastebin.com/pKXtCnDX
>
>
>
> I’m using master + I cherry-picked your commit:
>
> Here are the top 3 commits in git log: http://pastebin.com/UzFf0wNV
>
>
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com]
> *Sent:* Friday, January 27, 2017 5:06 PM
> *To:* Paraskevopoulos Georgios <geo...@intracom-telecom.com>
> *Cc:* Manuel Buil <mb...@suse.com>; opnfv-us...@lists.opnfv.org;
> opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli <
> vlingadaha...@mvista.com>
>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi George,
>
> Thanks for testing it.
>
> Could you please share content of /etc/hiera.
>
> Which version of the odl plugin do you use?
>
> I believe this patch doesn't cause the error above with duplicate
> declaration.
>
>
>
> On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi Michael,
>
>
>
> I tested your patch. Now it fails with a different error
>
> 2017-01-27 14:13:19ERRDuplicate declaration:
> L3_clear_route[default] is already declared; cannot redeclare at
> /etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on
> node node-3.domain.tld
>
>
>
> Can you look into it?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Paraskevopoulos
> Georgios
> *Sent:* Friday, January 27, 2017 2:15 PM
> *To:* Michael Polenchuk <mpolenc...@mirantis.com>; Manuel Buil <
> mb...@suse.com>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org;
> Veena Lingadahalli <vlingadaha...@mvista.com>
>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Michael,
>
>
>
> DPDK is not a requirement for SFC. NSH is. I can help you with the
> debugging.
>
> I’ll try your patch now to see if it will resolve the issue and get back
> to you.
>
>
>
> BR,
>
&
Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing with br-aux not found
Hi George,
This commit is intended only for 9.0 branch of odl plugin
(i.e. for Fuel 9/mitaka).
On Fri, Jan 27, 2017 at 7:23 PM, Paraskevopoulos Georgios <
geo...@intracom-telecom.com> wrote:
> Hi Michael,
>
>
>
> There is only one file, astute.yaml
>
> Here are the contents: http://pastebin.com/pKXtCnDX
>
>
>
> I’m using master + I cherry-picked your commit:
>
> Here are the top 3 commits in git log: http://pastebin.com/UzFf0wNV
>
>
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com]
> *Sent:* Friday, January 27, 2017 5:06 PM
> *To:* Paraskevopoulos Georgios <geo...@intracom-telecom.com>
> *Cc:* Manuel Buil <mb...@suse.com>; opnfv-us...@lists.opnfv.org;
> opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli <
> vlingadaha...@mvista.com>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi George,
>
> Thanks for testing it.
>
> Could you please share content of /etc/hiera.
>
> Which version of the odl plugin do you use?
>
> I believe this patch doesn't cause the error above with duplicate
> declaration.
>
>
>
> On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi Michael,
>
>
>
> I tested your patch. Now it fails with a different error
>
> 2017-01-27 14:13:19ERRDuplicate declaration:
> L3_clear_route[default] is already declared; cannot redeclare at
> /etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on
> node node-3.domain.tld
>
>
>
> Can you look into it?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Paraskevopoulos
> Georgios
> *Sent:* Friday, January 27, 2017 2:15 PM
> *To:* Michael Polenchuk <mpolenc...@mirantis.com>; Manuel Buil <
> mb...@suse.com>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org;
> Veena Lingadahalli <vlingadaha...@mvista.com>
>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Michael,
>
>
>
> DPDK is not a requirement for SFC. NSH is. I can help you with the
> debugging.
>
> I’ll try your patch now to see if it will resolve the issue and get back
> to you.
>
>
>
> BR,
>
> George
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com
> <mpolenc...@mirantis.com>]
> *Sent:* Friday, January 27, 2017 12:55 PM
> *To:* Manuel Buil <mb...@suse.com>
> *Cc:* brady.allen.john...@ericsson.com; Paraskevopoulos Georgios <
> geo...@intracom-telecom.com>; opnfv-tech-discuss@lists.opnfv.org;
> opnfv-us...@lists.opnfv.org; Veena Lingadahalli <vlingadaha...@mvista.com>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Manuel,
>
> Is dpdk the requirement for SFC?
>
> I've successful deployment with https://review.openstack.org/421907, but
> for now ... vms don't want to receive ip from dhcp server.
> ("dpdkvhostuser" interface is being added to br-int, opendaylight
> controller looks fine & etc.)
> I'm definitely stuck a bit with it and have no much time to research an
> issue.
>
> It would be great if you could help me to debug it to get that I'm missing.
>
>
>
> On Fri, Jan 27, 2017 at 1:22 PM, Manuel Buil <mb...@suse.com> wrote:
>
> Hi Michael,
>
> How is the progress going? We are hitting today M5 in OPNFV and we cannot
> report if our SFC tests work due to this bug. Can we help somehow to
> accelerate this?
>
> Thanks,
> Manuel
>
>
>
>
>
> >>> Michael Polenchuk <mpolenc...@mirantis.com> 01/24/17 3:09 PM >>>
>
> Hi George,
>
> We're working on this now for Fuel9 support and will make the same for
> Fuel10 afterwards.
>
>
>
> On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi all,
>
>
>
> I am encountering the same problem in Fuel 10. Do we have any news on this?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Michael
> Polenchuk
> *Sent:* Monday, January 16, 2017 9:25 PM
> *To:* Veena Lingadahalli <vlingadaha...@mvista.com>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan]
Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing with br-aux not found
Hi George,
Thanks for testing it.
Could you please share content of /etc/hiera.
Which version of the odl plugin do you use?
I believe this patch doesn't cause the error above with duplicate
declaration.
On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios <
geo...@intracom-telecom.com> wrote:
> Hi Michael,
>
>
>
> I tested your patch. Now it fails with a different error
>
> 2017-01-27 14:13:19ERRDuplicate declaration:
> L3_clear_route[default] is already declared; cannot redeclare at
> /etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on
> node node-3.domain.tld
>
>
>
> Can you look into it?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Paraskevopoulos
> Georgios
> *Sent:* Friday, January 27, 2017 2:15 PM
> *To:* Michael Polenchuk <mpolenc...@mirantis.com>; Manuel Buil <
> mb...@suse.com>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org;
> Veena Lingadahalli <vlingadaha...@mvista.com>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Michael,
>
>
>
> DPDK is not a requirement for SFC. NSH is. I can help you with the
> debugging.
>
> I’ll try your patch now to see if it will resolve the issue and get back
> to you.
>
>
>
> BR,
>
> George
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com
> <mpolenc...@mirantis.com>]
> *Sent:* Friday, January 27, 2017 12:55 PM
> *To:* Manuel Buil <mb...@suse.com>
> *Cc:* brady.allen.john...@ericsson.com; Paraskevopoulos Georgios <
> geo...@intracom-telecom.com>; opnfv-tech-discuss@lists.opnfv.org;
> opnfv-us...@lists.opnfv.org; Veena Lingadahalli <vlingadaha...@mvista.com>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Manuel,
>
> Is dpdk the requirement for SFC?
>
> I've successful deployment with https://review.openstack.org/421907, but
> for now ... vms don't want to receive ip from dhcp server.
> ("dpdkvhostuser" interface is being added to br-int, opendaylight
> controller looks fine & etc.)
> I'm definitely stuck a bit with it and have no much time to research an
> issue.
>
> It would be great if you could help me to debug it to get that I'm missing.
>
>
>
> On Fri, Jan 27, 2017 at 1:22 PM, Manuel Buil <mb...@suse.com> wrote:
>
> Hi Michael,
>
> How is the progress going? We are hitting today M5 in OPNFV and we cannot
> report if our SFC tests work due to this bug. Can we help somehow to
> accelerate this?
>
> Thanks,
> Manuel
>
>
>
>
>
> >>> Michael Polenchuk <mpolenc...@mirantis.com> 01/24/17 3:09 PM >>>
>
> Hi George,
>
> We're working on this now for Fuel9 support and will make the same for
> Fuel10 afterwards.
>
>
>
> On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi all,
>
>
>
> I am encountering the same problem in Fuel 10. Do we have any news on this?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Michael
> Polenchuk
> *Sent:* Monday, January 16, 2017 9:25 PM
> *To:* Veena Lingadahalli <vlingadaha...@mvista.com>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi,
>
> This bug/feature could be tracked by
> https://bugs.launchpad.net/fuel-plugin-opendaylight/+bug/1656924
>
> We're going to get a support of ODL with DPDK usecase soon.
>
>
>
> On Tue, Jan 10, 2017 at 2:18 PM, Michael Polenchuk <
> mpolenc...@mirantis.com> wrote:
>
> Hi Veena,
>
> In case of DPDK enabled the br-aux bridge ain't created on compute nodes
> since physical(dpdk) interface is being connected directly to br-prv ovs
> bridge.
>
> I guess this case (ODL + OVS/DPDK) ain't supported yet.
>
> Please turn off "install dpdk" option and try it out.
>
>
>
> On Mon, Jan 9, 2017 at 8:18 PM, Veena Lingadahalli <
> vlingadaha...@mvista.com> wrote:
>
> Hi,
>
> I'm using opnfv fuel 9.0 to deploy openstack with ODL-SFC(netvirt) +
> OVS(DPDK+NSH). I have used all default plugins which are staged with the
> fuel iso.
> I have made the necessary configurations relate
Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?
Hi Bryan, You could use Fuel UI to avoid editing of yaml files: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html Anyway change of every value is not required. Usually network settings are modified (i.e. interfaces, networks, vlan range, ips & etc.). In most cases this is enough. http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide.html On Tue, Jan 24, 2017 at 10:17 PM, SULLIVAN, BRYAN L <bs3...@att.com> wrote: > Is there anyone on the FUEL team monitoring this list? Really, we cannot > make progress in Danube on Fuel support unless we get some basic support on > the issues we have with standing up a Fuel-based deploy for testing. > > > > Thanks, > > Bryan Sullivan | AT > > > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: > opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *SULLIVAN, > BRYAN L > *Sent:* Thursday, January 19, 2017 2:44 PM > *To:* Michael Polenchuk <mpolenc...@mirantis.com> > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test > in labs? > > > > Resending, as I have not yet see a clarification of the fields in the > dea-pod-override.yaml and dha.yaml files. I need this in order to setup our > PODs to test under Fuel for the Copper, Models, and VES project. > > > > Thanks, > > Bryan Sullivan | AT > > > > *From:* SULLIVAN, BRYAN L > *Sent:* Thursday, January 12, 2017 6:13 AM > *To:* 'Michael Polenchuk' <mpolenc...@mirantis.com> > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* RE: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test > in labs? > > > > Hi Michael, > > > > We figured out that much after actually looking at the README file, but > the details of the dea-pod-override.yaml and dha.yaml files are unclear, > i.e. how they should be setup for a specific POD, what are the options and > values, what’s mandatory/optional, etc. In the repo, it looks like they > refer to virtual envs, but after looking at the “secret” lab config > versions it’s not much clearer. There are dozens of fields, subnet specs, > etc and it’s unclear what they all related to. Where is the spec for all > that? > > > > Thanks, > > Bryan Sullivan | AT > > > > *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com > <mpolenc...@mirantis.com>] > *Sent:* Wednesday, January 11, 2017 11:35 PM > *To:* SULLIVAN, BRYAN L <bs3...@att.com> > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test > in labs? > > > > > > > > On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L <bs3...@att.com> wrote: > > Thanks for the help here and on IRC – much appreciated. > > One other question as asked on IRC: The deploy.sh script requires a "-b > base-uri" parameter which is the "stack-configuration" location. But there > is no spec of what needs to be at that location/resource (I’m assuming this > is an input, not output) - at least I can't find it. Any guidance? > > > > > > Hi Bryan, > > "-b base-uri" parameter usually pointed to the config which resides in the > repo, e.g.: > # git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel > > In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config > -s option is for a scenario name which is available in the repo as well > (.../opnfv-fuel/deploy/scenario). > > > -- > > Michael Polenchuk > Private Cloud / Mirantis Inc. > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?
On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L <bs3...@att.com> wrote: > Thanks for the help here and on IRC – much appreciated. > > One other question as asked on IRC: The deploy.sh script requires a "-b > base-uri" parameter which is the "stack-configuration" location. But there > is no spec of what needs to be at that location/resource (I’m assuming this > is an input, not output) - at least I can't find it. Any guidance? > > > > > Hi Bryan, "-b base-uri" parameter usually pointed to the config which resides in the repo, e.g.: # git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config -s option is for a scenario name which is available in the repo as well (.../opnfv-fuel/deploy/scenario). -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?
Hi Bryan, Please see answers inline ... > > Thanks for the link. I do look at the Jenkins status for high-level info, > but it’s hard to find out the things I need from that, which are, to start > related to how a developer deploys a simple fuel-based scenario (e.g. > os-nosdn-nonha) in the lab > > - What has changed since http://artifacts.opnfv.org/ > fuel/colorado/3.0/docs/installationprocedure/index.html (in general are > there any draft Danube docs yet) > As I know nothing significant has changed in terms of installation procedure. > - Is booting the fuel ISO the only option, or as with other > installers can we build/deploy on the fly with a simple bash script > (deploy.sh) after cloning the repo > Please refer at http://lists.openstack.org/pipermail/openstack-dev/2016-September/103969.html > - If booting the fuel ISO is the only option, what are the > requirements for the jumphost, e.g. can this be done in a virt-manager VM > (and how) or does it need to be bare metal, what are the host requirements > (minimum) for the jumphost, etc > This could be either virtual or baremetal (min RAM is ~2Gb, recommended 3Gb+ for fuel master node) > - How is virtual deployment of the fuel master achieved (the > install doc above does not specify the details) – it’s not clear if this is > different from booting the fuel ISO in a VM > deploy.sh script will do a trick (only thing is needed to install missing packages), it'll create all of vms, boot them ... and finally deploy a cluster as well: opnfv-fuel/ci# ./deploy.sh -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s no-ha_nfv-ovs_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso ready-to-use ISO you could get at http://artifacts.opnfv.org/fuel/latest.properties (OPNFV_ARTIFACT_URL=) > - If supported, what are the minimum requirements for virtual > deploy > RAM 10-11Gb for controllers, ram of computes depends on required workloads (1Gb+) > - What are the minimum requirements for bare metal lab servers, > e.g. as I have been using will this work > The same as above. -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing with br-aux not found
Hi Veena, In case of DPDK enabled the br-aux bridge ain't created on compute nodes since physical(dpdk) interface is being connected directly to br-prv ovs bridge. I guess this case (ODL + OVS/DPDK) ain't supported yet. Please turn off "install dpdk" option and try it out. On Mon, Jan 9, 2017 at 8:18 PM, Veena Lingadahalli <vlingadaha...@mvista.com > wrote: > Hi, > > I'm using opnfv fuel 9.0 to deploy openstack with ODL-SFC(netvirt) + > OVS(DPDK+NSH). I have used all default plugins which are staged with the > fuel iso. > I have made the necessary configurations related to neutron VLAN IDs, DPDK > enabled interface and Hugepage configuration in compute node. Network > verification is also successful. The deployment is failing with the below > error. > > generate_network_config(): Endpoint 'br-aux' not found in interfaces or > transformations result. at /etc/fuel/plugins/opendaylight > -0.9/puppet/manifests/odl-netconfig.pp:25 on node node-1.domain.tld > > I'm unable to check where this bridge is being created. Never faced this > issue before when neutron with tunneling is used. Am I missing any > configuration related to vlan? Attached the complete puppet log and > network_scheme. Please let me know the cause for error and how to proceed > about this. > > > Thanks, > -Veena > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [Fuel] [Functest] Fuel10, Newton and v3 testing
Hi Jose, Thank you for bringing this up. Please have a look at https://build.opnfv.org/ci/view/fuel/job/functest-fuel-virtual-daily-master/926/console The issue has gone after updating (by hand) of releng repo on CI host. I guess CI/infra team should take of it and get the reason why we've outdated releng repo on the CI hosts. On Thu, Dec 22, 2016 at 9:02 PM, Jose Lausuch <jose.laus...@ericsson.com> wrote: > Hi, > > Looking at the latest CI daily jobs for Fuel, Functest fails due to a > failure while running the healthcheck test case: > https://build.opnfv.org/ci/view/functest/job/functest- > fuel-baremetal-daily-master/1012/console > > I have ran Functest on Fuel-10 on a local server and got better results > after running some tests cases. > > > This output belongs to testing it with the ISO I got during the Plugfest: > fuel-10.0-1060-2016-12-02_23-00-01.iso --> http://pastebin.com/raw/ > uJ9R7mzT > > and with the latest ISO built in CI: > http://artifacts.opnfv.org/fuel/opnfv-2016-12-21_16-00-14.iso --> > http://pastebin.com/raw/S5RWcV8w > > > Both deployed virtual, NO-HA and without ODL. > > So, I don't understand what happens in CI, which is related to Glance [1] > but at least we don't have those v3 issues any more (thanks to Helen and > Serena from Functest team for fixing that). > > > [1] 2016-12-21 21:58:33,734 - healtcheck - INFO - Testing Glance API... > Error finding address for http://192.168.0.2:9292/v2/ > images/1a2969fc-5fb3-4d6b-bf3d-68fc889b0f41/file: Unable to establish > connection to http://192.168.0.2:9292/v2/images/1a2969fc-5fb3-4d6b- > bf3d-68fc889b0f41/file > > > Regards, > Jose > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] [FUEL][SDNVPN] ovs segfault
Hi, Please take into account Fuel 10/newton already has ovs 2.6.1 out of the box. (http://mirror.fuel-infra.org/mos-repos/ubuntu/10.0/pool/main/o/openvswitch/ ) On Mon, Dec 12, 2016 at 1:38 PM, Skiadas Romanos <r...@intracom-telecom.com> wrote: > Hi, > > I'm seeing an issue in ovs that exposes another issue with OpenDaylight. > This only happens with the ovs version compiled by the fuel plugin. > When the last tap interface is deleted (i.e. whenever the last VM on a > hypervisor is deleted), ovs segfaults, restarts and the wrong config is > pushed by ODL. The segfault does not happen with ovs 2.4 or stock 2.5 > stable. > We probably need to somehow address this because this is not really a > priority thing for ODL. It only happens when ovs restarts, normally or > abnormally like with a segfault. > > The things I have in mind to mitigate this are: > > 1) With ubuntu 16.04, we can probably just use stock ovs 2.5 for the VPN > deployment. This will make it incompatible with SFC and iirc integration > with SFC is one of the goals of the D release > 2) Wait until it is fixed upstream. It might take a long time for that to > be done (SR3?) > 3) uplift to ovs 2.6. George is working on a patch that uplifts fuel > plugin ovs to 2.6, I tested it and it seems that ovs no longer crashes. > > What are people's thoughts on this? > > BR, > Romanos > > > > > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > -- Michael Polenchuk Private Cloud / Mirantis Inc. ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
