Re: [opnfv-tech-discuss] Multisite termination and withdraws from Euphrates release

Hello, Is the TSC meeting time-slot 13:00~14:00 UTC on Aug.8? I will not able to attend the meeting through gotomeeting(it often takes long time to make it work, or sometimes don't work at all), but I can be there in IRC channel. Best Regards Chaoyi Huang(joehuang)

Re: [opnfv-tech-discuss] Multisite termination and withdraws from Euphrates release

Also adding the TSC mailing list. Thanks Joe for your work as the Multisite PTL. Can I schedule for a termination review on the TSC call on August 8th? Typical termination review takes about 10 minutes... Regards, Ray On Mon, Jul 24, 2017 at 5:40 PM, joehuang wrote: >

[opnfv-tech-discuss] Weekly Technical Discussion #95

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT

[opnfv-tech-discuss] Multisite termination and withdraws from Euphrates release

Hello, Considering that the project has reached its initial "requirement project" goals (not including integration): https://wiki.opnfv.org/display/PROJ/Requirements+Projects+Multisite Identify the requirements and gaps for the VIM (OpenStack) to support multi-site NFV cloud. A short summary

[opnfv-tech-discuss] fuel deployment, please help

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

[opnfv-tech-discuss] [release][documentation][euphrates] Milestone 6 - August 11

Team, As you know, one of the requirements for MS6 is preliminary documentation. At a minimum, the expectation is that you will have the directory structure and placeholder documents in place, based on a template, if available. In order to provide more clarity, I worked with Sofia to create a

Re: [opnfv-tech-discuss] Auto project proposal DCAE vs Policy

Hi, To continue on this thread, I think it was said that it should reflect that this covers the full scope of ONAP, even if the "release phases" have steps, it would be good to reflect that in the figure. A question regarding the relationship to Opera, does it make sense to have 2 projects

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Sounds great, we’ll be happy to see it pushed ☺ Best Regards, Ifat. From: Ciprian Barbu Date: Monday, 24 July 2017 at 19:37 To: "Afek, Ifat (Nokia - IL/Kfar Sava)" Cc: "opnfv-tech-discuss@lists.opnfv.org" , Ryota

Re: [opnfv-tech-discuss] error during deployment

Can you share the output of /var/log/fuel-agent-env-1.log please? -- Junaid On Mon, Jul 24, 2017 at 9:42 PM, Ishpreet Kaur wrote: > > Hello, > > I am trying to deploy fuel(brahmputra) on my ubuntu 14.04 lts , during > deployment after 42% i am getting an error saying

Re: [opnfv-tech-discuss] [release][euphrates] Milestone 5 / July 28

Reminder... On Thu, Jul 20, 2017 at 12:16 PM, David McBride < dmcbr...@linuxfoundation.org> wrote: > Team, > > Milestone 5 is just over one week away, on July 28. Here's a summary of > the requirements: > >- Completion of scenario integration for projects that rely on >scenarios for

[opnfv-tech-discuss] error during deployment

Hello, I am trying to deploy fuel(brahmputra) on my ubuntu 14.04 lts , during deployment after 42% i am getting an error saying provision has failed, ( following is an error i am getting during deployment of an environment) . Please give me suggestions , i would be really thankful to you. I had

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi, For Vitrage we actually started a Fuel plugin, it hasn’t been pushed upstream yet, mainly because Fuel is being replaced with MCP. It’s a rather simple plugin but it seems to do the job. We are interested in making it work with Doctor and Tacker for the moment, but we are still

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi, Thank you for the info. For Congress we looked for the doctor_driver.py but it simply wasn’t present in the Ubuntu package that the plugin installed, which came from Xenial. But there is a working version in Yakkety, which we used instead and for that we had to enable the Doctor

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi Ciprian, As Ryota stated, Vitrage is not officially recognized as a Doctor Inspector implementation, mainly because it is not supported in any of the OPNFV installers yet. I assume that you manually installed Vitrage on top of the Fuel deployment? Vitrage is able to respond to the Doctor

[opnfv-tech-discuss] [Barometer]

Hi, I would like to contribute to the project. Thank you, Brandon SDN/DCG ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

Hi Ciprian, Thank you for checking out Doctor project and reaching out us. In Danube, we officially support OpenStack Congress, but haven’t supported Vitrage yet. See, our release notes [1]. I’m not a fuel expert, but doctor driver in Congress may not be enabled in default, as it is not in

Re: [opnfv-tech-discuss] Auto project proposal DCAE vs Policy

I think that is a misinterpretation of my comment where the current text says "Policy (through DCAE)" where I proposed to strike "Through DCAE" as policy can be used by other modules as well, it wasn't suggested to state that NF should send data directly to policy. I assume Auto should test

Re: [opnfv-tech-discuss] Auto project proposal DCAE vs Policy

I'm not sure where the comment came from, but in order to get events to the policy engine they do have to be collected by DCAE and put on the message bus, so we will need both components to test that. Thanks, Bryan Sullivan | AT From: opnfv-tech-discuss-boun...@lists.opnfv.org

[opnfv-tech-discuss] Reply: [availability]High Availability Project meeting on Jul. 26

Hi all, I’ve finished the documents drafts of HA test cases for E release on etherpad: https://etherpad.opnfv.org/p/yardstick_ha_tc013 OpenStack Controller Messaging Queue Service High Availability https://etherpad.opnfv.org/p/yardstick_ha_tc014 OpenStack Controller Cluster Management

Re: [opnfv-tech-discuss] xci with mini flavor failed in ironic

On 24/07/17 09:56, Markos Chandras wrote: > On 24/07/17 09:44, Periyasamy Palanisamy wrote:>> [...] > > Tianwei(on CC) had the same issue a few days ago. I don't know it's > solved or not but perhaps he can shed some light here > [Retrying again with re-arranged headers since the CC was dropped

Re: [opnfv-tech-discuss] xci with mini flavor failed in ironic

On 24/07/17 09:44, Periyasamy Palanisamy wrote: > Hi Everyone, > > I am trying to install xci with mini flavor and looks like it fails > ironic enroll task [1]. > PFA full log. > > Thanks, > Periyasamy > > [1] > controller00]", "ok: [compute00]", "ok: [opnfv]", "", "TASK >

[opnfv-tech-discuss] [The Linux Foundation status] Subscription removed

We're sorry to see you go. This email confirms that you have unsubscribed from The Linux Foundation status updates. You can resubscribe at any time by visiting https://status.linuxfoundation.org.___ opnfv-tech-discuss mailing list