Hi Mazin, Lingli and all,
May I suggest applying this principle to all the community meetings? I noticed
that there are a couple of other meetings that have the same problem.
Thanks,
Huabing
Original Mail
Sender: ;
To:
Hi Kenny and Mazin,
As a result of the DST time change, the current time slot for ONAP calls are
technically one-hour later for regions that does not follow the practice in
winter, like China.
Hence a lot of them, including TSC weekly call, are now spanning after
mid-night.
As we requested
Oops. the meeting will be started from Nov 30, 2017.
As Nov 23, 2017 is holiday in US. many people would be absent.
Thanks,
On Mon, Nov 20, 2017 at 10:56:37AM -0800,
Isaku Yamahata wrote:
> According to doodle result, I decided the following time slot.
> The
According to doodle result, I decided the following time slot.
The meeting will be held from
Thur Nov 23, 2017 6:00PM-7:00PM(PST)/02:00(UTC)/10:00am(CST)
I've requested meeting creation. If it's not created in time
I'll use my free zoom account. In that case I'll announce it.
> time slot: Weekly
Hi, Michael,
According to AAI SMEs, this is the way to do it:
1. SDN switch by Pnf
2. SDN switch port by p-interface and l-interface(s)
3. Physical links and logical links between SDN port switches by physicallinks
and logicallinks
4. SDN switch locations by complexes.
5. If the SDN control
Hi Brian,
Yes this is the error message in the SO SDNCAdapter debug log as the return
from SDNC.
Also, when executing preload from robot vm we got error in reading Json
replying into dictionary. We have raised a JIRA ticket for the same.
https://jira.onap.org/browse/INT-342
Further, we still
Doc Team,
Here is the agenda so far for tomorrow's meeting.
https://wiki.onap.org/display/DW/2017-11-19+Doc+Project+Meeting.
The general topics are below. Also note the JIRA Issues for each
https://jira.onap.org/secure/RapidBoard.jspa?rapidView=37=DOC
* Wiki Migration
* Structure
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
Share with your friends & peers :-)
Best Regards,
-kenny
> Begin forwarded message:
>
> From: Jill Lovato
> Subject: [lf_staff] Today's ONAP News
> Date: November 20, 2017 at 6:23:04 AM PST
> To: Linux Foundation Staff
>
> Good
Hi
I wonder if it would not be helpful for the whole community to manage
the list of project contributors and commiters in the repo.
in OPNFV we got an INFO file when we list the people. See example for
one of the project here: https://git.opnfv.org/functest/tree/INFO
in this file we got
Hi
The folder 'ansible-vvp-voluems' is missing in the 'devkit' project.
Expected under:
../vvp/devkit/ansible/roles
Note that a different folder named 'ansible-vvp-bootstrap' is present in this
location.
Thanks
Moshe Hoadley
972-9-77-62712
This message and the information
Hello,
At one point in time it was user admin and password
Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of
More info:
This is the command vagrant gets stuck on:
INFO ssh: Execute: cat /tmp/vagrant-network-entry_eth2 >>
/etc/sysconfig/network-scripts/ifcfg-eth2
if command -v nmcli &>/dev/null; then
if command -v systemctl &>/dev/null && systemctl -q is-enabled NetworkManager
&>/dev/null; then
Hi
My dev env is Ubuntu 16. The virtualization framework is virtualbox.
The current status is that when running 'vagrant up', it is able to boot the
vm ' pxe_ops_01...'.
At this point vagrant gets stuck on network configuration:
devel@devel:~/dev/onap/vvp/devkit$ vagrant up
Bringing machine
14 matches
Mail list logo