date:20181109

Re: [opnfv-tech-discuss] Intent to Participate in the OPNFV Hunter Release #release #hunter

2018-11-09 Thread David McBride

Team,

Just a reminder that we've reached the halfway point in the
intent-to-participate window for the Hunter release.  The window will close
in two weeks on Nov 23 (MS1). While I've heard from many of you, there are
still several projects that have not responded.  If you're one of those,
please send your intent email ASAP.

In addition, please remember that the end of the intent-to-participate
window also marks MS1, at which time your project release plan is
required.  Recall that projects may create a release plan that is suitable
for their needs.  However, if you are a new project, and you have no idea
what to do for a release plan, you may use this template
,
although it is not required.

Finally, we have now passed the point at which a project proposal could be
submitted and be approved in time to join the release, without a milestone
exception.

Let me know if you have any questions.

David

On Mon, Oct 29, 2018 at 6:46 AM David McBride 
wrote:

> Team,
>
> Today marks the opening of the intent-to-participate window for the
> Hunter release (i.e. MS0).  Please find the procedure here
> .
> The window closes as of MS1, tentatively planned for Nov 23.
>
> Please let me know which release track you intend to participate in by
> including *one* of the following statements in your intent to participate
>  notification:
>
>1. We intend to follow the traditional track.
>2. We intend to follow the continuous delivery track
>3. We intend to follow both the traditional track and the continuous
>delivery track
>
> Also, please remember that if you are planning a new project for the
> Hunter release, you have until Nov 9 to submit your proposal to the TSC
> and still have time to be approved and to join the release before the
> intent-to-participate window closes.
>
> Let me know if you have questions.  Thanks.
>
> David
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22337): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22337
Mute This Topic: https://lists.opnfv.org/mt/27781534/21656
Mute #release: https://lists.opnfv.org/mk?hashtag=release=2783016
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Docs in containers

2018-11-09 Thread Mark Beierl

Random thought: for those projects that supply containers with a ReST front 
end, it would be a nice addition to have the html format of the documentation 
served locally.

However, the current directory structure, with tox.ini in the root of the 
project, and docs as a subdir, does not lend itself to building a docs 
container, as that means the docker build context needs to include the full 
project.  Another limitation is the opnfv-docker.sh script does not call any 
scripts in the target, it simply calls docker build right in the specified 
directory, meaning I cannot cp from ../docs.

So, I’m just throwing this discussion out there to see if anyone else has any 
thoughts on how to approach this.

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mark.bei...@dell.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22336): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22336
Mute This Topic: https://lists.opnfv.org/mt/28055523/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] #opnfv-docs build for StorPerf failing

2018-11-09 Thread Mark Beierl

Hello, all

Not sure who can help me with this.  The storperf-rtd-verify-master build is 
failing [1], so I cannot commit my release notes.  Anyone know what is 
happening here?

11:19:04 error in setup command: 'install_requires' must be a string or list of 
strings containing valid project/version requirement specifiers

[1] https://build.opnfv.org/ci/job/storperf-rtd-verify-master/7/console

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mark.bei...@dell.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22334): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22334
Mute This Topic: https://lists.opnfv.org/mt/28050224/21656
Mute #opnfv-docs: https://lists.opnfv.org/mk?hashtag=opnfv-docs=2783016
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] Intent to Participate in the OPNFV Hunter Release #sdnvpn #release #hunter

2018-11-09 Thread Nikos Karandreas

Hi,



The purpose of this mail is to notify the OPNFV TSC that the SDNVPN project 
intends to participate in the OPNFV Hunter release.

We intend to follow both the traditional track and the continuous delivery 
track.



Best Regards

Nikos

(acting on behalf of SDNVPN)





From: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of David McBride
Sent: Monday, October 29, 2018 3:47 PM
To: TECH-DISCUSS OPNFV 
Cc: Bin Hu ; TSC OPNFV 
Subject: [opnfv-tech-discuss] Intent to Participate in the OPNFV Hunter Release 
#release #hunter



Team,



Today marks the opening of the intent-to-participate window for the Hunter 
release (i.e. MS0).  Please find the procedure  
 here.  
The window closes as of MS1, tentatively planned for Nov 23.



Please let me know which release track you intend to participate in by 
including one of the following statements in your intent to participate 
notification:

1. We intend to follow the traditional track.

2. We intend to follow the continuous delivery track

3. We intend to follow both the traditional track and the continuous 
delivery track

Also, please remember that if you are planning a new project for the Hunter 
release, you have until Nov 9 to submit your proposal to the TSC and still have 
time to be approved and to join the release before the intent-to-participate 
window closes.



Let me know if you have questions.  Thanks.



David



--

David McBride

Release Manager, OPNFV

Mobile:   +1.805.276.8018

Email/Google Talk:   
dmcbr...@linuxfoundation.org

Skype: davidjmcbride1

IRC: dmcbride



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22333): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22333
Mute This Topic: https://lists.opnfv.org/mt/27781534/21656
Mute #release: https://lists.opnfv.org/mk?hashtag=release=2783016
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter=2783016
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] [Auto] huawei-pod12 ONAP status

2018-11-09 Thread Elias Richard

Hi Harry,


Tina has forwarded me the information below, but this does not solve my issue.


The issue I emailed you about is concerning the ssh access into the Openstack 
VMs, as is shown by this command run by the deploy-onap.sh script:

"ssh -o StrictHostKeychecking=no -i /root/.ssh/onap_key ubuntu@172.30.12.114 
'sudo docker ps'" which returns "Permission denied (publickey)."

I cannot access the logs without accessing the VMs. I have been going through 
other public and private keys mentioned in the installation, but still no luck.

Could you try connecting to host1 and accessing one of the VMs?


Thank you very much,

Richard


From: Tina Tsou 
Sent: 09 November 2018 05:35:16
To: Elias Richard
Cc: huangxiangyu; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org; Gary Wu
Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status

Dear Richard et al,

Harry had a look, the docker tag in the environment doesn’t match what’s in the 
code, you need to look at the log and change accordingly.


Thank you,
Tina

On Nov 5, 2018, at 8:12 AM, Elias Richard 
mailto:richard.el...@tieto.com>> wrote:


Hello,

As was recommended by Tina I have added Gary to the conversation.


Thank you for the fix Harry, looks like the nbi_docker value was also some 
problem with the python packages. The VMs do all start up now, but I have 
problems connecting to them with ssh so I can look over the logs. Even the last 
command of the deployment script does not complete correctly as it returns a 
permission problem with the private key. So far I am not sure if it is a 
problem with the ssh config or if the VMs are not loading the proper ssh public 
key.


Have you encountered this problem? Is there any specific ssh configuration 
necessary for the pod or ONAP?


Thank you very much,

Richard


From: huangxiangyu mailto:huangxiang...@huawei.com>>
Sent: 05 November 2018 08:11:07
To: Elias Richard; Klozik Martin; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status


Hi Richard



I have removed the pip.conf for host1. Though pip will still check the local 
repo first but it can install packages from internet now.

There seems no stack at this point and I believed OpenStack components are 
working functionally.

As for nbi_docker, I haven’t met this problem before, maybe you need to find 
answer from ONAP community



Regards

Harry



发件人: Elias Richard [mailto:richard.el...@tieto.com]
发送时间: 2018年10月30日 21:36
收件人: Klozik Martin mailto:martin.klo...@tieto.com>>; 
huangxiangyu mailto:huangxiang...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status



Hi Harry,

I connected to the host and run the commands, but there were problems with the 
python packages.



There was a proxy server set for the pip installation which cannot download the 
packages. Was there a reason a proxy was necessary for pip? If the packages are 
already installed the check could probably be skipped.



There are also some parts of Openstack that seem to be stuck after the reboot( 
for example a stack with status:DELETE_FAILED). The teardown script tries to 
remove this, but as it is stuck there could be problems with the deployment.



The creation script itself returns this error:

"ERROR: The Parameter (nbi_docker) was not provided."

I was not able to find this parameter in any of the templates in 
~/onap/integration/test/ete/labs/ so I am not sure what is missing.



I started analyzing the problem but I did not want to change anything before 
asking you for help.

Could you please take a look at it and share any insights you have?

Thank you very much,

Richard



From: Klozik Martin
Sent: 29 October 2018 14:36:37
To: huangxiangyu; 
opnfv-tech-discuss@lists.opnfv.org
Cc: Elias Richard
Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status



adding Richard to the loop...



--Martin



Od: 
opnfv-tech-discuss@lists.opnfv.org 
mailto:opnfv-tech-discuss@lists.opnfv.org>> 
za uživatele Klozik Martin 
mailto:martin.klo...@tieto.com>>
Odesláno: středa 24. října 2018 8:00
Komu: huangxiangyu; 
opnfv-tech-discuss@lists.opnfv.org
Předmět: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status



Hi Harry,



thank you for the hints, we will go ahead with ONAP re-deployment as suggested.



Best Regards,

Martin



Od: huangxiangyu mailto:huangxiang...@huawei.com>>
Odesláno: středa 24. října 2018 5:01:37
Komu: Klozik Martin; 
opnfv-tech-discuss@lists.opnfv.org
Předmět: RE: [Auto] huawei-pod12 ONAP status



Hi Martin



On host1

Re: [opnfv-tech-discuss] Commiter rights for yardstick #yardstick #opnfv-tech-discuss

2018-11-09 Thread limingjiang

Hi helpdesk,

Could you help to check and resend the invite to 
volodymyrx.myt...@intel.com ?
The vote link is as in [1]. Thank you in advance.

[1] https://gerrit.opnfv.org/gerrit/#/c/63635/

Best Regards,
Rex Lee

+---+
[cid:image001.png@01D0A50A.DD5A8F20]
+ Mingjiang Li (Rex) Mobile: +86 13761275017
+ Shanghai Institute, Huawei
+ No. , Xinjinqiao Road, Pudong, Shanghai, 201206, P.R.China
+---+

From: opnfv-tech-discuss@lists.opnfv.org 
[mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of Abhijit Sinha
Sent: Friday, November 09, 2018 6:24 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Commiter rights for yardstick #yardstick 
#opnfv-tech-discuss

Hi OPNFV team,

Volodymyr has been approved as a commiter as a committer in OPNFV yardstick 
project but he didn't get the invite and hence doesn't have the commiter rights 
yet.
Can someone please help here.


Regards,
Abhijit
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22331): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22331
Mute This Topic: https://lists.opnfv.org/mt/28047295/21656
Mute #yardstick: https://lists.opnfv.org/mk?hashtag=yardstick=2783016
Mute #opnfv-tech-discuss: 
https://lists.opnfv.org/mk?hashtag=opnfv-tech-discuss=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Commiter rights for yardstick #yardstick #opnfv-tech-discuss

2018-11-09 Thread Abhijit Sinha

Hi OPNFV team,

Volodymyr has been approved as a commiter as a committer in OPNFV yardstick 
project but he didn't get the invite and hence doesn't have the commiter rights 
yet.
Can someone please help here.

Regards,
Abhijit
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22330): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22330
Mute This Topic: https://lists.opnfv.org/mt/28047295/21656
Mute #yardstick: https://lists.opnfv.org/mk?hashtag=yardstick=2783016
Mute #opnfv-tech-discuss: 
https://lists.opnfv.org/mk?hashtag=opnfv-tech-discuss=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

2018-11-09 Thread Tomi Juvonen

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Juvonen, Tomi (Nokia - FI/Espoo)":MAILTO:tomi.juvo...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kunzmann, 
 Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Manuel Bui
 l:MAILTO:mb...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Ferriter, 
 Cian":MAILTO:cian.ferri...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Shobhan Ay
 yadevaraSesha (sayyadev):MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Oravainen,
  Juha (Nokia - FI/Espoo)":MAILTO:juha.oravai...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rautakumpu
 , Mika (Nokia - FI/Espoo)":MAILTO:mika.rautaku...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
DESCRIPTION;LANGUAGE=en-US:--Changed to every second week--\nDoctor is a fa
 ult management and maintenance project to develop and realize the conseque
 nt implementation for the OPNFV reference platform.\n\nMore details:\nhttp
 s://etherpad.opnfv.org/p/doctor_meetings\nJoin from PC\, Mac\, Linux\, iOS
  or Android: https://zoom.us/j/2362828999\nOr iPhone one-tap :\nUS: +16699
 006833\,\,2362828999# or +16465588656\,\,2362828999#\nOr Telephone:\nDial(
 for higher quality\, dial a number based on your current location):\nUS: +
 1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855
  880 1246 (Toll Free)\nMeeting ID: 236 282 8999\nInternational numbers ava
 ilable: https://zoom.us/zoomconference?m=Xn-Kas4jq2GuyfbCCKYpwvi6FpHEYX8n\
 n\n\n
RRULE:FREQ=WEEKLY;UNTIL=20191223T10Z;INTERVAL=2;BYDAY=MO;WKST=MO
UID:04008200E00074C5B7101A82E00890BEE3A7E4CFD301000
 01D2D1BD7816FC84E8F8E2D91ED20C728
SUMMARY;LANGUAGE=en-US:OPNFV Doctor weekly meeting
DTSTART;TZID=UTC:20181119T10
DTEND;TZID=UTC:20181119T11
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20181109T095130Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:21
LOCATION;LANGUAGE=en-US:zoom
X-MICROSOFT-CDO-APPT-SEQUENCE:21
X-MICROSOFT-CDO-OWNERAPPTID:1500071906
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-LOCATIONS:[{"DisplayName":"zoom"\,"LocationAnnotation":""\,"Loc
 ationUri":""\,"LocationStreet":""\,"LocationCity":""\,"LocationState":""\,
 "LocationCountry":""\,"LocationPostalCode":""\,"LocationFullAddress":""}]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22329): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22329
Mute This Topic: https://lists.opnfv.org/mt/28047123/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] Intent to Participate in the OPNFV Hunter Release #release #hunter

[opnfv-tech-discuss] Docs in containers

[opnfv-tech-discuss] #opnfv-docs build for StorPerf failing

Re: [opnfv-tech-discuss] Intent to Participate in the OPNFV Hunter Release #sdnvpn #release #hunter

Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status

Re: [opnfv-tech-discuss] Commiter rights for yardstick #yardstick #opnfv-tech-discuss

[opnfv-tech-discuss] Commiter rights for yardstick #yardstick #opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

8 matches

Site Navigation

Mail list logo

Footer information